The following pages and posts are tagged with

TitleTypeExcerpt
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...
Creating test cases - Java Page You can create a new test case or suit by extending TestNGTestCase. More specific flavor for web services is WSTestCase and for web and mobile is WebDriverTestCase. Now you can create test same as in TestNG. If you are new to TestNG, here is...
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...
KWD Custom Step Definition Page Steps can be defined in kwl The Basic Step definition is following. STEP-DEF|<stepName>|{"description":"<meaningfull step description>",<meta-key>:<meta-value>} <first stepName>|<step input parameters>|<step out parameters> ... <nth stepName>|<step input parameters>|<step out parameters> END|| While execution make sure required kwl files are mentioned in step.provider.pkg property as below <div class="language-properties...
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
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.
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.
Test Data Page {% include inline_image.html file="worddavbc574dd694d63ef066aa760b1d31af80.png" alt="Test Data Diagram" %} ## Properties: You can create properties file as per your requirement under resources dir. Properties will be available in your test case and test page. You can directly access by **props/pageProps** object available at test/page level. Example: String someprop = props.getString("some.property"); ##...