title: FluentAssertions ShouldBeEquivalentTo() versus Should().BeEquivalentTo()
body: <p>I have a test that verifies the collection output of a method. This variation of the test passes:</p>
  
  <pre><code>    [TestMethod, TestCategory("BVT")]
      public void TheStatusesAreReturned()
      {
          var expectedUnprocessedStatuses = new List&lt;FileUploadStatus&gt;
              {
                  FileUploadStatus.InProcess,
                  FileUploadStatus.Pending,
              };
  
          Sut.GetUnprocessedStatuses()
              .Should()
              .BeEquivalentTo(expectedUnprocessedStatuses);
      }
  </code></pre>
  
  <p>This variation of the test fails, with the error "Expected item[0] to be InProcess, but found Pending":</p>
  
  <pre><code>    [TestMethod, TestCategory("BVT")]
      public void TheStatusesAreReturned2()
      {
          var expectedUnprocessedStatuses = new List&lt;FileUploadStatus&gt;
              {
                  FileUploadStatus.InProcess,
                  FileUploadStatus.Pending,
              };
  
          Sut.GetUnprocessedStatuses()
              .ShouldBeEquivalentTo(expectedUnprocessedStatuses);
      }
  </code></pre>
  
  <p>Clearly, <code>ShouldBeEquivalentTo</code> cares about collection item order, whereas <code>BeEquivalentTo</code> does not. Why is the notion of equivalency different between the 2 methods?</p>