Training activity information
Details
Implement and document a formal testing protocol for a piece of software
Type
Developmental training activity (DTA)
Evidence requirements
Evidence the activity has been undertaken by the trainee​.
Reflection on the activity at one or more time points after the event including learning from the activity and/or areas of the trainees practice for development.
An action plan to implement learning and/or to address skills or knowledge gaps identified.
Considerations
- Local protocols and guidelines
- Governance
- Documentation
- Management of software updates
Reflective practice guidance
The guidance below is provided to support reflection at different time points, providing you with questions to aid you to reflect for this training activity. They are provided for guidance and should not be considered as a mandatory checklist. Trainees should not be expected to provide answers to each of the guidance questions listed.
Before action
- What are the key components of a formal testing protocol? What different types of software testing should you consider? How should the testing process be documented?
- What principles of software testing do you aim to apply and learn from? What experience do you expect to gain in creating and executing test cases? How will this DTA improve your understanding of software quality assurance?
- What testing methodologies or frameworks will you research? How will you identify the critical functionalities of the software that need to be tested? What tools or techniques might you use for test management and documentation? What are your initial thoughts on how to approach the development of a formal testing protocol?
In action
- Pay attention to your actions in creating the testing protocol.
- How are you currently approaching the task of defining test cases, procedures, and expected outcomes?
- What types of testing are you including and why?
- How are you structuring the documentation?
- What decisions are you making regarding the scope of testing, the level of detail in the protocol, and the tools or methods you might use?
- What aspects of test protocol creation feel intuitive based on your understanding of software testing principles, and what requires more conscious effort in applying those principles to a specific piece of software?
- How effective are your current choices in developing a comprehensive and practical testing protocol that can adequately verify the software’s functionality and identify potential defects?
- What challenges are you encountering as you try to anticipate different test scenarios and document them effectively?
- What can you learn about the process of software testing and protocol development as you are actively creating this protocol?
- How does this activity connect to your existing knowledge of software quality assurance and testing methodologies?
- Are there alternative approaches you could be considering for structuring the testing protocol or the types of tests included?
- What support or guidance might you need at this moment if you had access to the software requirements or specifications?
- Are you ensuring your testing protocol aligns with best practices for software testing and documentation?
On action
- Describe the software you developed the testing protocol for. Summarise the key components of your formal testing protocol (e.g., test cases, procedures, expected outcomes). Note any challenges you faced in designing and documenting the testing protocol.
- What are the essential elements of a formal software testing protocol?
- How did the process of creating the protocol influence your understanding of software quality assurance?
- What considerations are important when documenting a testing protocol for others to use?
- How does a formal testing protocol contribute to the overall software development lifecycle?
- What principles of formal testing will you apply in future software development projects?
- What tools or techniques can you use to improve the efficiency and effectiveness of your testing protocols?
- How will you ensure that testing is an integral part of your development process?
Beyond action
- Have you looked back at the testing protocol you implemented and documented? How does your understanding of software testing principles and documentation best practices compare now? Have you been involved in other testing activities since?
- How has this activity enhanced your understanding of the importance of rigorous testing in ensuring software quality and reliability? Has it influenced your approach to testing or reviewing software in other contexts?
- What transferable skills, such as attention to detail, systematic thinking, and technical writing, did you develop? What clear actions can you take to further develop your skills in software testing methodologies and documentation standards?
Relevant learning outcomes
| # | Outcome |
|---|---|
| # 4 |
Outcome
Use good software design and programming practice. |
| # 5 |
Outcome
Use programming languages. |
| # 7 |
Outcome
Develop a protocol for testing a piece of software. |