Skip to content

Test case summary printer

Jump to bottom
vvolverine edited this page Nov 5, 2018 · 1 revision

Main concept

By default Sprimber integrated with Allure report framework and all test scenario results available in Allure compatible Json format. But time to time more convenient to have faster feedback from console logs about test execution. For this Sprimber able to provide two printers:

  • TestCaseIlluminator - simple listener implementation of all possible Sprimber events
  • TestCaseSummaryPrinter - listener implementation that happens on finish events or test case started event.

TestCaseIlluminator

This printer enable by default and each event that occurred in the system logged at debug level. To enable logs from tihs printer DEBUG log level should be set for this package, like

logging:
  level:
    com.griddynamics.qa.sprimber.lifecycle.TestCaseIlluminator: DEBUG

TestCaseSummaryPrinter

This realization more similar to original Cucumber/JBehave console printer implementations. By default it is disabled and it is recommended to enable it only during local executions, depends on log size. To enable it, next properties should be set sprimber.configuration.summary.printer.enable=true, example sprimber: configuration: summary: printer: enable: true

Simple output will looks like:

Test Case Started: Scenario to check failed steps
  Before from: public void com.griddynamics.qa.sprimber.test.steps.BaseEchoSteps.before()
    When some when action with param 'hi' [hi] (PASSED) 
    Then every time failed action [] (FAILED) 
  After from: public void com.griddynamics.qa.sprimber.test.steps.BaseEchoSteps.after()
Clone this wiki locally