Fix failing mtermvector integration test

Author: gmarz

src/Nest/Document/Multiple/MultiTermVectors/MultiTermVectorsResponse.cs

@@ -11,6 +11,8 @@ public interface IMultiTermVectorsResponse : IResponse
 	[JsonObject]
 	public class MultiTermVectorsResponse : ResponseBase, IMultiTermVectorsResponse
 	{
+		// TODO For 3.0 we should create a separate term vector object rather than using TermVectorsResponse
+		// since it contains general response data that isn't relevant (i.e. ApiCall, StatusCode, etc...)
 		[JsonProperty("docs")]
 		public IEnumerable<TermVectorsResponse> Documents { get; internal set; } = new List<TermVectorsResponse>();
 	}

src/Tests/Document/Multiple/MultiTermVectors/MultiTermVectorsApiTests.cs

@@ -48,7 +48,8 @@ protected override LazyResponses ClientUsage() => Calls(
 
 		protected override void ExpectResponse(IMultiTermVectorsResponse response)
 		{
-			response.Documents.Should().NotBeEmpty().And.HaveCount(2).And.OnlyContain(d => d.Found).And.OnlyContain(d => d.IsValid);
+			response.IsValid.Should().BeTrue();
+			response.Documents.Should().NotBeEmpty().And.HaveCount(2).And.OnlyContain(d => d.Found);
 			var termvectorDoc = response.Documents.FirstOrDefault(d => d.TermVectors.Count > 0);
 
 			termvectorDoc.Should().NotBeNull();

src/Tests/tests.yaml

@@ -1,5 +1,5 @@
 # mode either u (unit test), i (integration test) or m (mixed mode)
-mode: m
+mode: i
 # the elasticsearch version that should be started
 elasticsearch_version: 2.0.1
 # whether we want to forcefully reseed on the node, if you are starting the tests with a node already running