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

fix(browser): ensure browser state is EXECUTING when tests start #3074

Merged
merged 3 commits into from
Jul 23, 2018
Merged

fix(browser): ensure browser state is EXECUTING when tests start #3074

merged 3 commits into from
Jul 23, 2018

Commits on Jul 5, 2018

  1. fix(browser): ensure browser state is EXECUTING when tests start

    Browser state is EXECUTING when it actually started to execute tests. This state change is triggered by client on actual tests execution start.
    Alexei Solodovnicov committed Jul 5, 2018
    Configuration menu
    Copy the full SHA
    69ab0d7 View commit details
    Browse the repository at this point in the history

Commits on Jul 23, 2018

  1. fix(browser): introduced an additional browser state CONFIGURING

    The CONFIGURING state means that the browser is already not READY for tests, as someone has requested tests execution (and provided a config file). But the provided config file is not yet processed, configuration is not applied and the tests execution is not yet started, so the browser is not yet at EXECUTING state.
    Alexei Solodovnicov committed Jul 23, 2018
    Configuration menu
    Copy the full SHA
    88b6a74 View commit details
    Browse the repository at this point in the history
  2. fix(browser): refactored browser state names

    Alexei Solodovnicov committed Jul 23, 2018
    Configuration menu
    Copy the full SHA
    65799d3 View commit details
    Browse the repository at this point in the history