-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor/test version config #3649
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just left a small comment about std redirection
build/scripts/Testing.fs
Outdated
@@ -54,7 +53,10 @@ module Tests = | |||
| (true) -> [ "--logger"; "trx"; "--collect"; "\"Code Coverage\""; "-v"; "m"] |> List.append command | |||
| _ -> command | |||
|
|||
Tooling.DotNet.ExecInWithTimeout "src/Tests/Tests" commandWithCodeCoverage (TimeSpan.FromMinutes 30.) | |||
// using std redirection since that foces vstest not to redirect Console.Write from Elastic.Xunit somehow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this comment be updated with how vstest and xunit communicate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reverting this since Proc
is not happy on linux
/// </summary> | ||
public bool ShowElasticsearchOutputAfterStarted { get; } = true; | ||
|
||
/// <summary> When specified will only run one overload in API tests, helpful when debugging locally </summary> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comments 💯
…on was a tad too complicated
…starting the tests this fix's vstest breaking console.writeline though I am not quite sure yet as to why
41511e1
to
138a0b0
Compare
…ixed launching of cluster on command line not doing any bootstrap. Made environment config mode decision explicit rather then inferred based of NEST_INTEGRATION_VERSION
* small fixes to how default versions are resolved and test configuration was a tad too complicated * refactor ITestConfiguration a bit further, use console redirect when starting the tests this fix's vstest breaking console.writeline though I am not quite sure yet as to why * Execute tests without standard redirection for now * AssertStatusCode called base.AssertResponse on SearchUsageTestBase, fixed launching of cluster on command line not doing any bootstrap. Made environment config mode decision explicit rather then inferred based of NEST_INTEGRATION_VERSION (cherry picked from commit 5403c8a)
ported to master |
ITestConfiguration
and its implementations.