6 Educators providing Courses about Testing in Coventry

SAFe® Agile Software Engineering: In-House Training The introduction of Lean-Agile and DevOps principles and practices into software engineering has sparked new skills and approaches that help organizations deliver higher-quality, software-centric solutions faster and more predictably. This workshop-oriented course explores foundational principles and practices and how continuous flow of value delivery and built-in quality are enabled by XP technical practices, Behavioral-Driven Development (BDD), and Test-Driven Development (TDD). Attendees will learn proven practices to detail, model, design, implement, verify, and validate stories in the SAFe® Continuous Delivery Pipeline, as well as the practices that build quality into code and designs. Attendees will also explore how software engineering fits into the larger solution context and understand their role in collaborating on intentional architecture and DevOps. What you will Learn To perform the role of a SAFe® Agile Software Engineer, you should be able to: Define Agile Software Engineering and the underlying values, principles, and practices Apply the Test-First principle to create alignment between tests and requirements Create shared understanding with Behavior-Driven Development (BDD) Communicate with Agile modeling Design from context for testability Build applications with code and design quality Utilize the test infrastructure for automated testing Collaborate on intentional architecture and emergent design Apply Lean-Agile principles to optimize the flow of value Create an Agile Software Engineering plan Introduction to Agile Software Engineering Connecting Principles and Practices to Built-in Quality Accelerating Flow Applying Intentional Architecture Thinking Test-First Discovering Story Details Creating a Shared Understanding with Behavior-Driven Development (BDD) Communicating with Models Building Systems with Code Quality Building Systems with Design Quality Implementing with Quality

Assuring Quality Through Acceptance Testing: In-House Training It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?