Skip to content
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

Split IT into different classes #514

Merged
merged 2 commits into from
Feb 19, 2018
Merged

Split IT into different classes #514

merged 2 commits into from
Feb 19, 2018

Conversation

dadoonet
Copy link
Owner

This way we gain:

  • Classes dedicated for some use cases
  • More readable, more maintainable
  • Parallel execution of the suite

Local tests showed that we gain a faster execution from 03:37 to 02:09 with 77 tests ran by 26 suites instead of 4 suites.

This way we gain:

* Classes dedicated for some use cases
* More readable, more maintainable
* Parallel execution of the suite

Local tests showed that we gain a faster execution from 03:37 to 02:09 with 77 tests ran by 26 suites instead of 4 suites.
@dadoonet dadoonet added update When updating an existing feature test Related to tests only labels Feb 19, 2018
@dadoonet dadoonet added this to the 2.5 milestone Feb 19, 2018
@dadoonet dadoonet self-assigned this Feb 19, 2018
On 5.x or 6.x platinum series, elasticsearch answers with a 401 error.

Closes #515.
@dadoonet dadoonet merged commit c9270ca into master Feb 19, 2018
@dadoonet dadoonet deleted the pr/split-tests branch February 19, 2018 11:24
dadoonet added a commit that referenced this pull request Feb 19, 2018
With recent changes like #500 and #514 it takes much more time to run all tests from the IDE when elasticsearch is not running yet locally.
The reason is that we start a new elasticsearch test container for every class. Starting a container can take some time.

We should try to reduce that and share the same docker instance for all tests.

Closes #516
dadoonet added a commit that referenced this pull request Feb 19, 2018
With recent changes like #500 and #514 it takes much more time to run all tests from the IDE when elasticsearch is not running yet locally.
The reason is that we start a new elasticsearch test container for every class. Starting a container can take some time.

We should try to reduce that and share the same docker instance for all tests.

Closes #516
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Related to tests only update When updating an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant