Overview

For Supporting test plan it usefull to see the statistic of unimplemented tests and step by step adding new one.
The purpouse of that document is to desribe steps which allows to see that statistic in generated cucumber report.

Steps to apply

First of we need to add @Undefined anotation to our empty scenarios

 @Undefined
  Scenario: Undefined scenario one
    * print 'undefined'

The rules is the next
- Add @Undefined anotation above scenario
- Put the only one print 'with any text'
- The text in the print may describe your scenario more detailed if you want

Example of undefined test file
https://github.com/folio-org/folio-integration-tests/blob/ddefcdf9ecf48ec3215fdfbb939b3f5683a13600/acquisitions/src/main/resources/domain/mod-finance/features/undefined.feature

Run scenario with Junit as usual test file throu runFeatureTest method
See example:
https://github.com/folio-org/folio-integration-tests/blob/ddefcdf9ecf48ec3215fdfbb939b3f5683a13600/acquisitions/src/test/java/org/folio/FinanceApiTest.java#L137

@Test
void undefinedTests() {
	runFeatureTest("undefined");
}

Jenkins Cucumber Report

See actual report:
FOLIO Reference Builds -> folio-api-tests-karate -> Cucumber reports
https://jenkins-aws.indexdata.com/job/FOLIO_Reference_Builds/job/folio-api-tests-karate/168/cucumber-html-reports/overview-features.html

Currently Cucumber report threat Undefined tests as failed

Browser not supported