The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| BDD Custom Step Definition | Page | Steps can be defined in bdl The Basic Step definition is following. STEP-DEF:<meaningfull step description> [Keyword] <first step description with parameters> … [Keyword] <nth step description> END While execution make sure required bdl files are mentioned in step.provider.pkg property as below <pre... |
| BDD Keyword Synonyms | Page | Default BDD Keywords : Given,When,Then,And,Using,Having,With Modify/Change this keywords with required Keyword, by specifying property as below For Example : Given=Provided;GivenThat “Given“ synonym enables “Provided” and “GivenThat” use case of such feature can be where user want to have BDD in different language other than English... |
| Define Test Suite | Page | Behavior driven test suite consist of one or more Scenarios. Each scenario represents one test case. One can provide optional related information as background or narrative or user-story related to scenarios authored in the suite. Save your suite file with .bdd extension. Formation of Suite <div class="language-plaintext... |
| Describe Test Step | Page | Test step can be defined in .java (coded) or .bdl (code-less) files. Test step consists of implementation and description, with which it is known. Description is also used to reporting the step. Description must have same number of placeholder as number of arguments expected in step. The argument placeholder can... |
| Test Step Metadata | Page | Supports for Custom Meta-Data at test step level. Example: Here, groups is a custom meta-data for step. JAVA @MetaData(value = "{'groups':['login']}") @QAFTestStep(description = "user login with username {username} and password {password}") public void login(String username,String password) { //To-do } BDD STEP DEF <div... |
| Test Step Threshold and time tracking | Page | Test Step Threshold In Built ‘threshold’ Test Step Meta-Data Support. Example: Login Step should be executed in 10s, if takes more than 10s then it displays as warning in report. User can specify threshold value by following way, Java Step @QAFTestStep(description = "user logins with... |
| BDD2 | Page | QAF BDD2 is derived from QAF BDD and gherkin. It supports meta-data from qaf bdd as tags and examples from gherkin. |
| BDD2 meta-data | Page | Scenario metadata provides information to help manage a scenario.The meta-data are collected as part of the BDD parsing. |
| Comment and line break in BDD | Page | QAF BDD supports single line and multiline comment |
| Configuring BDD for execution | Page | QAF BDD supports single line and multiline comment |
| BDD Generator | Page | BDD Generator is useful to generate BDD2 feature file that can be used to review or to share with others. |
| BDD-step | Page | QAF BDD2 is derived from QAF BDD and gherkin. It supports meta-data from qaf bdd as tags and examples from gherkin. |
| BDD syntax | Page | QAF supports multiple BDD syntaxes. |
| QAF Gherkin Scenario Factory | Page | Author tests in standard Gherkin format that Cucumber understands with power of QAF as back-end |
| Metadata rules | Page | Meta data rules can be defiened to enforce meta-data and it's possible value for the project |
| Runtime Scenario | Page | QAF support BDD in pure java enables development team to follow behavior driven development approach for test automation implementation in best efficient way. |
| Scenario | Page | Scenario consist of meta-data and sequence of steps to represents a single test case. Each step can be started with standard BDD keywords [Given | When | The... |
| Test case meta-data | Page | Testcase meta-data provides information to help manage a test case.The meta-data are collected as part of the BDD parsing. |