Ability to only run one test section in file in yaml test runner #4404
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
You can now pass -s "Test section name" to the rest-api-spec test runner to only run a single test inside a file. Before you could only filter to a file as whole. This also makes sure args with spaces are quoted when passing down from our build tooling (super rudimentary) We now emit Skip messages during the run so we can see the test itself skipped. Because in our current flow we run the test setup before evaluating the `skip` block its hard to see nothing happened because things are happening (setup requests) Lastly the proxy detection now includes `xpack` test suite. `mitmproxy -k` will work if we reroute https traffic to it.
github-actions bot
pushed a commit
that referenced
this pull request
Feb 21, 2020
You can now pass -s "Test section name" to the rest-api-spec test runner to only run a single test inside a file. Before you could only filter to a file as whole. This also makes sure args with spaces are quoted when passing down from our build tooling (super rudimentary) We now emit Skip messages during the run so we can see the test itself skipped. Because in our current flow we run the test setup before evaluating the `skip` block its hard to see nothing happened because things are happening (setup requests) Lastly the proxy detection now includes `xpack` test suite. `mitmproxy -k` will work if we reroute https traffic to it.
github-actions bot
pushed a commit
that referenced
this pull request
Feb 21, 2020
You can now pass -s "Test section name" to the rest-api-spec test runner to only run a single test inside a file. Before you could only filter to a file as whole. This also makes sure args with spaces are quoted when passing down from our build tooling (super rudimentary) We now emit Skip messages during the run so we can see the test itself skipped. Because in our current flow we run the test setup before evaluating the `skip` block its hard to see nothing happened because things are happening (setup requests) Lastly the proxy detection now includes `xpack` test suite. `mitmproxy -k` will work if we reroute https traffic to it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You can now pass -s "Test section name" to the rest-api-spec test runner
to only run a single test inside a file. Before you could only filter to
a file as whole.
This also makes sure args with spaces are quoted when passing down from
our build tooling (super rudimentary)
We now emit Skip messages during the run so we can see the test itself
skipped. Because in our current flow we run the test setup before
evaluating the
skipblock its hard to see nothing happened becausethings are happening (setup requests)
Lastly the proxy detection now includes
xpacktest suite.mitmproxy -kwill work if we reroute https traffic to it.