en-us/about_ATDD.TestScriptor.help.txt
|
TOPIC
about_atdd.testscriptor SHORT DESCRIPTION Define with ATDD.TestScriptor ATDD test scenarios and convert it into AL code LONG DESCRIPTION The Acceptance Test-Driven Development test scriptor allows the user to define in a managed matter ATDD test scenarios and convert it into a code structure to facilate fast test code development. At this moment this conversion is only implemented for .al Optional Subtopics An ATDD pattern is defined by so called tags: - FEATURE: defines what feature(s) the test or collection of test cases is testing - SCENARIO: defines for a single test the scenario being teste - GIVEN: defines what data setup is needed; a test case can have multiple GIVEN tags when data setup is more complex - WHEN: defines the action under test; each test case should have only one WHEN tag - THEN: defines the result of the action, or more specifically the verification of the result; if multiple results apply, multiple THEN tags will be needed EXAMPLES {{ Code or descriptive examples of how to leverage the functions described. }} NOTE {{ Note Placeholder - Additional information that a user needs to know.}} TROUBLESHOOTING NOTE {{ Troubleshooting Placeholder - Warns users of bugs}} {{ Explains behavior that is likely to change with fixes }} SEE ALSO {{ See also placeholder }} {{ You can also list related articles, blogs, and video URLs. }} KEYWORDS {{List alternate names or titles for this topic that readers might use.}} - {{ Keyword Placeholder }} - {{ Keyword Placeholder }} - {{ Keyword Placeholder }} - {{ Keyword Placeholder }} |