You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there are more than 1 Feature sections in the test file:
the browser/page does NOT close after each test, so at the end I have many browsers opened, which slowing down my system.
the After and AfterSuite hooks are NOT working at all (are NOT called).
Tests behave (passed/failed) normally and the next test is conducted on newly opened browser, but After and AfterSuite hooks are NOT even called after test(s). Additional hooks / teardown implemented in the codecept.conf do NOT help. Any suggestion?
What do you get instead?
Tests behave (passed/failed) normally and the next test is conducted on newly opened browser, but After and AfterSuite hooks are NOT even called after test(s). Additional hooks / teardown implemented in the codecept.conf do NOT help, so at the end I have many browsers/threads opened, which slowing down my system.
What are you trying to achieve?
When there are more than 1
Feature
sections in the test file:After
andAfterSuite
hooks are NOT working at all (are NOT called).Tests behave (passed/failed) normally and the next test is conducted on newly opened browser, but
After
andAfterSuite
hooks are NOT even called after test(s). Additional hooks / teardown implemented in thecodecept.conf
do NOT help. Any suggestion?What do you get instead?
Tests behave (passed/failed) normally and the next test is conducted on newly opened browser, but
After
andAfterSuite
hooks are NOT even called after test(s). Additional hooks / teardown implemented in thecodecept.conf
do NOT help, so at the end I have many browsers/threads opened, which slowing down my system.Details
The text was updated successfully, but these errors were encountered: