Wednesday, May 14, 2014
6:30 PM
Agenda
• Getting started with Pilot projects for TDD (Test Driven Development) /BDD (Behavior Driven Design)
• 6:30 PM - Professional Networking and Social Time
• 7:00 PM - Presentation Starts
Overview:
Creating "measurable quality expectations" at the beginning of the development cycle forms a contract between the business domain and software development units. This contract represents the core of Behavior Driven Development (BDD). The tools used to fulfill each role in BDD form robust testing framework which lends to reliable, repeatable testing. Implementation off BDD may vary, but each framework should address the following functional requirements:
1. Consist of a modular design allowing for various functional modules to be replaced without impacting functionality.
2. Plain language, standardized, testing script dialect: Business Readable DSL (Domain Specific Language)
3. Standardized test execution
4. Automated test script to unit test translation and mapping
5. Ability to inject testing data into individual test scenarios
6. View state agnostic or able to adapt to pre-defined views
7. Persist and test results at runtime
8. Provide a centralized repository for captured elements, test data, test handler configurations
9. Provide a user interface for view element data, managing test data, assigning test handlers
10. Provide or report code coverage analysis
Presenter: Jerry Davison
Jerry is a lead architect at DST Systems. During the past three years he has provided leadership in quality improvements resulting in several innovative solutions. His accomplishments include leading a major effort in the migration of code repositories and devised a production deployment model that has been adapted by the DST enterprise. He is currently implementing Behavior Driven Development through his efforts in designing an automated testing framework. His leadership and architectural influence have spread across the enterprise allowing him to sit on a number advisory boards covering a broad range of concerns that include deployment processes, service architecture, quality assurance and automation.
Sponsor: DST Systems / [email protected]
• Getting started with Pilot projects for TDD (Test Driven Development) /BDD (Behavior Driven Design)
• 6:30 PM - Professional Networking and Social Time
• 7:00 PM - Presentation Starts
Overview:
Creating "measurable quality expectations" at the beginning of the development cycle forms a contract between the business domain and software development units. This contract represents the core of Behavior Driven Development (BDD). The tools used to fulfill each role in BDD form robust testing framework which lends to reliable, repeatable testing. Implementation off BDD may vary, but each framework should address the following functional requirements:
1. Consist of a modular design allowing for various functional modules to be replaced without impacting functionality.
2. Plain language, standardized, testing script dialect: Business Readable DSL (Domain Specific Language)
3. Standardized test execution
4. Automated test script to unit test translation and mapping
5. Ability to inject testing data into individual test scenarios
6. View state agnostic or able to adapt to pre-defined views
7. Persist and test results at runtime
8. Provide a centralized repository for captured elements, test data, test handler configurations
9. Provide a user interface for view element data, managing test data, assigning test handlers
10. Provide or report code coverage analysis
Presenter: Jerry Davison
Jerry is a lead architect at DST Systems. During the past three years he has provided leadership in quality improvements resulting in several innovative solutions. His accomplishments include leading a major effort in the migration of code repositories and devised a production deployment model that has been adapted by the DST enterprise. He is currently implementing Behavior Driven Development through his efforts in designing an automated testing framework. His leadership and architectural influence have spread across the enterprise allowing him to sit on a number advisory boards covering a broad range of concerns that include deployment processes, service architecture, quality assurance and automation.
Sponsor: DST Systems / [email protected]
Posts
0 Response to "May 14th: KCJava Kansas City Java User Group Meeting - TDD and BDD"
Post a Comment