1 / 14

郭旻灝 102522014

Proposing Regulatory-Driven Automated Test Suites Patrick Morrison, Casper Holmgreen , Aaron Massey, Laurie Williams. 郭旻灝 102522014. We propose the use of Behavior-Driven-Development (BDD) technology to create these test suites. Behavior-Driven-Development(BDD).

ronnie
Download Presentation

郭旻灝 102522014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposing Regulatory-Driven Automated Test SuitesPatrick Morrison, Casper Holmgreen, Aaron Massey, Laurie Williams 郭旻灝 102522014

  2. We propose the use of Behavior-Driven-Development (BDD) technology to create these test suites

  3. Behavior-Driven-Development(BDD) • BDD is a specialized version of test-driven development which focuses on behavioral specification • BDD does not have any formal requirements for exactly

  4. With BDD, desired system behavior with respect to regulatory requirements can be captured as constrained natural language ‘scenarios’.

  5. goal: enable organizations to compare their systems to regulation in a repeatable and traceable way through the use of BDD • Step • Identify Regulations • Develop Scenarios • Automate Scenarios

  6. Identify Regulations • Develop Scenarios • Automate Scenarios • Select regulatory text • Identify each regulation with which a system must comply

  7. Identify Regulations • Develop Scenarios • Automate Scenarios • Be associated with each tested regulation to validate its achievement • Takes the form of a detailed set of instructions readable by a person • Traceability • name clearly • contain a reference to the specific section of regulation

  8. Identify Regulations • Develop Scenarios • Automate Scenarios • Write code for adapting regulatory to a system • appropriate roles • sequences of steps • verification conditions • Split the code in to a structured natural language component

  9. Establishes a baseline for the development of the acceptance test suite • Provides a suite of tests that can be compared against other means of testing

  10. Test Suite • Establish the link between regulations and the behavior of the tested system. • ensuring each aspect of the regulation is represented by one or more scenarios

  11. Coding Scheme “SFIP” • S:Define a scenariothat correctly represents its segment of theregulation • F: the system provides thefunction required by the scenario • I: the step code implements thesteps called for by the scenario • P: he system passes the scenarioas executed

  12. Conclusion • Define scenarios for clearly defined regulatory texts • Build system-specific step files to execute the scenarios • BDD can be used to describe system behavior in scenarios that both users and developers can use

  13. Step was defined in a full programming language • Using BDD acceptance test suites to support checking of regulatory requirements

  14. Thanks for your listening

More Related