Skip to content

GTest without filter separation #144

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

Merged
merged 2 commits into from
Jun 2, 2017
Merged

GTest without filter separation #144

merged 2 commits into from
Jun 2, 2017

Conversation

muggenhor
Copy link
Contributor

@muggenhor muggenhor commented Apr 6, 2017

The HookRegistrationFixture didn't do all it needed to do in its SetUp method. When running all test cases in a single source file at once this caused test failures.

This PR both fixes that fixture (1a7b7b1) and runs the entire test suite at once, in addition to separated, to detect these kinds of failures in the future (04011a8).

This is the failure exposed by the different test execution (04011a8): https://travis-ci.org/muggenhor/cucumber-cpp/builds/219301662

I.e. otherwise we don't ever validate the proper execution of SetUp()
and TearDown().
@muggenhor muggenhor closed this Apr 6, 2017
@muggenhor muggenhor reopened this Apr 6, 2017
@muggenhor muggenhor merged commit 1a7b7b1 into cucumber:master Jun 2, 2017
muggenhor added a commit that referenced this pull request Jun 2, 2017
I.e. running all cases in a single process, without respawning for every
test case, is now possible without a failure.
@muggenhor muggenhor deleted the gtest-without-filter-separation branch June 2, 2017 14:13
@muggenhor muggenhor added this to the v0.4.1 milestone Jun 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant