Fix GRAPH related integration tests due to

stricter validation on ES's side

Author: Mpdreamz

paket.lock

@@ -1,10 +1,7 @@
 NUGET
-  remote: http://api.nuget.org/v3/index.json
-  specs:
-    AsciiDocNet (1.0.0-alpha3)
-    ShellProgressBar (3.0)
   remote: https://www.nuget.org/api/v2
   specs:
+    AsciiDocNet (1.0.0-alpha3)
     Bogus (3.0.5-beta-2)
       Newtonsoft.Json (>= 8.0.2) - framework: >= net40, dnx451, dnxcore50
       System.ComponentModel (>= 4.0.1-beta-23516) - framework: dnxcore50

src/Tests/Framework/Integration/Bootstrappers/Seeder.cs

@@ -152,6 +152,10 @@ public static PropertiesDescriptor<Project> ProjectProperties(PropertiesDescript
 						)
 					)
 				)
+				.Text(s=>s
+					.Name(p=>p.Description)
+					.Fielddata()
+				)
 				.Date(d => d
 					.Name(p => p.StartedOn)
 				)

src/Tests/XPack/Graph/Explore/GraphExploreApiTests.cs

@@ -48,7 +48,7 @@ protected override LazyResponses ClientUsage() => Calls(
 					vertices = new [] {
 						new
 						{
-							field = "numberOfCommits",
+							field = "name",
 							size = 500,
 							min_doc_count = 20,
 							shard_min_doc_count = 1,
@@ -79,7 +79,7 @@ protected override LazyResponses ClientUsage() => Calls(
 				.Connections(cc=>cc
 					.Query(q=>q.MatchAll())
 					.Vertices(v=>v
-						.Vertex(p=>p.NumberOfCommits, gv=>gv
+						.Vertex(p=>p.Name, gv=>gv
 							.MinimumDocumentCount(20)
 							.ShardMinimumDocumentCount(1)
 							.Size(500)
@@ -118,7 +118,7 @@ protected override LazyResponses ClientUsage() => Calls(
 					{
 						new GraphVertexDefinition
 						{
-							Field = Field<Project>(p=>p.NumberOfCommits),
+							Field = Field<Project>(p=>p.Name),
 							MinimumDocumentCount = 20,
 							ShardMinimumDocumentCount = 1,
 							Size = 500,

src/Tests/tests.yaml

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