Software Testing 13th Nov

• AI
• Higher Education (non-degree)

Software Testing 

C1 Test evaluation and presentation of results 

Lesson Aim:

To enable learners to understand what elements make a good test plan and evaluate what they create.

Lesson Recap: 

Summary of Results:

After testing, all findings and observations are compiled into an understandable summary. This includes key metrics, defects found, and any relevant statistics that demonstrate the overall software quality.

Acceptance Testing

This final phase of testing verifies that the software meets business requirements and user needs. It is typically performed by end-users or stakeholders and focuses on validating that the system is fit for deployment and use in real-world scenarios.

Regression Testing:

Performed after changes or updates to the software, regression testing ensures that new code does not negatively affect existing functionality. This helps maintain software stability and quality throughout the development lifecycle.

Intended Learning Outcomes:

At the end of the lesson the learners will be able to:

Analyse software test results to identify and document any undocumented bugs accurately.

Evaluate test outcomes to provide justified, high-quality recommendations for improving the software.

Understand presentation techniques for the next assignment 

Who typically performs acceptance testing, and what is its main purpose?

1. Developers, to check code quality
2. Project managers, to create project reports
3. Testers, to check security vulnerabilities
4. End-users or stakeholders, to validate the system meets requirements

What is the primary goal of regression testing?

1. To enhance software design
2. To validate user interface elements
3. To check whether new changes introduce new defects
4. To optimize code performance

Which scenario best describes when both acceptance testing and regression testing should be performed?

1. Before the requirements are gathered, to check initial ideas
2. After major updates—to ensure the system meets user expectations and that previous functionalities still work as intended
3. Only after minor spelling corrections
4. Only during project planning, before any code is written

Share one bug you have encountered when using different pieces of software

Test Result Analysis- Recap

Test result analysis summarises the testing process and outcomes to provide insight into software quality and performance.

Key elements include total test cases executed, passed, failed, blocked/skipped cases.

It evaluates test coverage to show how much of the product was tested, including functional, code, and performance aspects.

Defects found are categorised by severity and priority, with assessments of business impact and resolution status.

The analysis helps identify trends, such as modules with recurring issues or issues in the testing process.

Test environment details and any challenges affecting results are noted for reproducibility.

The final summary supports decision-making with recommendations on areas for improvement and overall test effectiveness.

Peer Task! 

Work in pairs to review the provided list of software testing outcome reports.

Each report contains examples of both documented and undocumented bugs, for each discuss and identify which are documented or undocumented. 

Make notes on any patterns you see and the impact of missing documentation

Intended Learning Outcomes:

• Learners will analyse software test results to identify and document any undocumented bugs accurately.

• Learners will evaluate test outcomes to provide justified, high-quality recommendations for improving the software.

• Learners will prepare to present their evaluation findings and recommendations clearly and confidently demonstrating communication skills.

Think, Pair, Share 

Think – 5 minutes

Individually review your previous work to recall how to distinguish between documented and undocumented bugs.

Reflect on the characteristics and impact of undocumented bugs in software testing.

Pair – 10 minutes

Move to a different PC and join your assigned partner.

Together, analyse the provided list of bug reports.

Compile a list of undocumented bugs, providing reasons for your selections.

Share – 10 minutes

Selected pairs present their findings to the class.

Accept feedback and observations from peers to refine your understanding.

Share feedback to class from paired work

Intended Learning Outcomes:

• Learners will analyse software test results to identify and document any undocumented bugs accurately.

• Learners will evaluate test outcomes to provide justified, high-quality recommendations for improving the software.

• Learners will prepare to present their evaluation findings and recommendations clearly and confidently demonstrating communication skills.

Presentation Skills! 

Presentation Skills! 

Body Language 

Stand tall with shoulders relaxed; avoid slouching.

Use purposeful hand gestures to emphasize key points—hold gestures briefly, avoid nervous fidgeting or repetitive movements.

Keep hands visible; avoid crossing arms or putting hands in pockets.

Face the audience with open body posture to appear confident and approachable.

Use movement deliberately to engage audience areas—not aimless pacing.

Clarity and Tone 

Clarity	Tone
Speak clearly and at a moderate pace Use simple language, avoid jargon Pause between key points	Vary pitch and volume to maintain interest Use a warm and friendly tone Match tone to message content

Eye Contact/Additional Tips

Maintain eye contact with different audience members to build connection.

Avoid staring at notes or slides excessively.

For virtual presentations, look at the camera to simulate eye contact.

Smile genuinely to create warmth.

Use facial expressions that align with your message to reinforce meaning.

Practice frequently to reduce nervousness and improve natural delivery.

Record yourself or practice in front of a mirror for feedback.

Engage audience with questions or quick interactions to maintain focus.

Random Topics 

Freddie and Marty- Why Mondays should be optional 

Jonny and Cormac- How to survive a zombie apocalypse with household items

Adam and Zach- The funniest autocorrect fails 

Kamil and Daniel-  Weirdest inventions to ever exist 

Ryan McV and Eben- How to become a professional procrastinator 

Ryan McAteer and Ryan Quinn- If animals could talk what would they say 

Intended Learning Outcomes:

• Learners will analyse software test results to identify and document any undocumented bugs accurately.

• Learners will evaluate test outcomes to provide justified, high-quality recommendations for improving the software.

• Learners will prepare to present their evaluation findings and recommendations clearly and confidently demonstrating communication skills.