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

Output during tests execution #45

Closed
20 tasks done
OndraM opened this issue Jan 15, 2016 · 1 comment
Closed
20 tasks done

Output during tests execution #45

OndraM opened this issue Jan 15, 2016 · 1 comment

Comments

@OndraM
Copy link
Member

OndraM commented Jan 15, 2016

Currently output of all tests is printed in the console output right after each test is finished. This makes the output a bit messy and is not always necessary. We should use output levels (default, verbose, very verbose, debug) to make the output more helpful in different situations.

Output levels distribution

Standard level

Use-case: I just want to run everything and I care only about test results count, not about the cause of errors etc.

Verbose level (-v)

Use-case: I want to run tests locally and see some basic startup/status/progress information during the run. If some test fails, I want to know which one. (But don't care about exact error message.).

  • Basic startup configuration info (version, browser, environment,)
  • Name of failed test

Very verbose level (-vv)

Use-case: I want to run tests locally and see detailed startup/status/progress information during the run. If something happens during the run, I want to know where and what exactly.

  • Detailed startup configuration info (all run-time config, selenium server URL, log path, etc.)
  • Test started/unqueued/finished
  • Error output of failed tests
  • Process timeout error

Debug level (-vvv)

Use-case: I am debugging some tests and want all available information, see what starts and when; OR the tests are run on CI server (and the output is stored for possible later investigation)

  • List of found files, testcases and their dependencies and delays on startup
  • Command line of started process
  • All output and error output from tests
  • With this level the DEBUG variable is passed to each PHPUnit process, thus tis output is added to the test output:
    • Executed WebDriver commands

Uncategorized messages

  • "Testcase "%s" is prepared to be run" (currently in debug level)
  • 'Testcase "%s" is queued to be run %01.1f minutes after testcase "%s" is finished' (currently debug)
  • 'Running command for class ...' (currently debug)
  • 'No tasks left, exiting the execution loop...'
  • 'Process for class "%s" finished'
  • 'Unqueing class "%s"'

Messages from the PHPUnit process

  • "Initializing "%s" WebDriver for "%s::%s" (from the PHPUnit process)
  • Destroying "%s" WebDriver for "%s::%s" (session %s) (from the PHPUnit process)
  • "Test failed on page "%s", taking page snapshots" "Screenshot saved to file ..." "HTML snapshot saved to file" (from the PHPUnit process)
  • "Starting execution of test %s" (from the PHPUnit process)
  • "Finished execution of test %s" (from the PHPUnit process)

Any thoughts, ideas, comments?

@OndraM OndraM changed the title Output during tests execution Output during tests execution [RFC] Jan 15, 2016
OndraM added a commit to OndraM/steward that referenced this issue Jan 29, 2016
OndraM added a commit to OndraM/steward that referenced this issue Jan 29, 2016
OndraM added a commit to OndraM/steward that referenced this issue Jan 29, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 12, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 12, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 12, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 13, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 13, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 13, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 13, 2016
OndraM added a commit to OndraM/steward that referenced this issue Feb 13, 2016
@OndraM OndraM changed the title Output during tests execution [RFC] Output during tests execution Feb 13, 2016
@OndraM
Copy link
Member Author

OndraM commented Feb 26, 2016

#46 is now merged, will be released in 1.3.0.

@OndraM OndraM closed this as completed Feb 26, 2016
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

No branches or pull requests

1 participant