q12

PROJECT TESTING
This presentation covers the Testing component of a Final Year Project.
n

by nurazzah abubakar
 FINAL YEAR PROJECT JOURNEY
Proposal 1
The project begins with a proposal
outlining the goals and scope of the
final year project. 2 Requirement Gathering & Analysis
The next step is to gather requirements and
analyze the needs for the project.
Low-fidelity prototyping 3
Low-fidelity prototypes are created to
test initial ideas and concepts.
4 High-fidelity prototyping
More detailed high-fidelity prototypes are
Testing then developed.
5
The prototypes undergo thorough testing
to ensure the project meets
requirements. 6 Exhibition
The final project is showcased at an
exhibition for feedback and evaluation.
Final documentation 7
The project journey concludes with
comprehensive final documentation.
na
 INTRODUCTION
1 Definition 2 Purpose
A process of executing a program or Primary purpose of testing is to detect
application with the intent of finding the software
software bugs. failures, so that defects may be discovered and
corrected.
A process of validating and verifying that a
software program or application or product:
3 Importance
▪ Meets the business and technical
requirements. Testing is a critical phase in the software
▪ Works as expected. development lifecycle, ensuring the quality
▪ Can be implemented with the same and functionality of IT projects.
characteristic.
 Why Software Testing Is Needed?
1 No software developer is perfect 2 Catching defects sooner rather
▪ Developing software is a complex task,
than later
▪ Late detection is hard to fix.
hence errors are anticipated.
▪ Reduce the risks of software failures
▪ Software defects cost the US $2.08
trillion in 2023, risen from $60mil in
2002.

3 Stability 4 Customer advocacy/satisfaction

▪ Development process is less stressful if ▪ Developers are paid for the job & QA
chaos to overcome defects could be engineers have a role to ensure the
reduced. software meets customer’s
requirements and expectations.
 Testing Types
1 Functionality test 2 Non-functionality test
▪ Activities that verify a specific action or ▪ Test the aspects of the software that may not
function of the code. be related to a specific function or user
▪ Focus on validating the software against action.
the requirements/specifications ▪ Includes:
▪ Includes: ▪ Scalability
▪ Basic usability test ▪ Performance
▪ User Acceptance test (UAT) ▪ Behavior under certain constraints
▪ Installation test ▪ Security
▪ Development test ▪ Compatibility
▪ Destructive test
▪ Recovery test
 USABILITY/USER TESTING
▪ A technique used in
user-centered
interaction design to
evaluate a product by
testing it on users.
▪ Gives direct input on
how real users use the
system.
 Objectives
1 2 3
Identifying problems with Uncover opportunities to Learning about target user’s behavior
the design of the improve. and preferences.
products or services.
Core Elements
Testing Scene
 Usability Testing Techniques

Observation Interviews Surveys Task-based Testing

Watch users Conduct one-on- Use surveys to Assign specific
interact with the one interviews to collect tasks and observe
software and note gather in-depth quantitative data how users navigate
their behaviors and feedback and and broader user and complete
pain points. insights from feedback on the them.
users. software.
 Usability Testing Evaluation Methods
1 Traditional usability test 2 Online usability test (unmoderated)
(moderated)
• Many participants participated at the same
▪ Field test (at least 30 participants). time.
▪ Involves one-on-one session between a • It is set up in the similar way as the field test.
moderator and a test participants. • Participants go through the scripted
▪ The moderator provides tasks to be predefined tasks and their behaviors are
completed by the participants. logged automatically.
▪ The moderator records the participants
behaviors and response to questions.
▪ Self-reported metric can also be used.
 Factors To Consider
Budget & Timeline Participants Ethics Data Collection & Clean up
▪ Expenses needed for ▪ Who are the actual ▪ How does the ▪ Procedure or methods
conducting the users of the test protect the for collecting the data.
lab/field test. E.g. system/app? participants’ ▪ Software tool to assist
paper, photocopy, food, ▪ How to approach and privacy? E.g. in data analysis.
stationery etc. recruit them? Secrecy of ▪ Cleaning incomplete
▪ Duration for ▪ What kind of incentive their personal data and outliers.
conducting the test should be given? information
etc.
Planning for Usability Testing
1 Prepare the materials for the usability test and print
necessary documents (e.g. information sheet, consent
form, task sheet, etc.).

2 Conduct the test.

3 Analyze the data and prepare the graphical

presentation of the results.
 Example of
Questionnaire
 USER ACCEPTANCE TEST (UAT)
▪ Consists of a process of verifying that a solution works for the user, or determining if the
requirements of a specification or contract are met prior to its delivery.
▪ System is delivered to the user or customer for acceptance testing.
▪ Basically is done by the user or customer although other stakeholders may be involved as well.
 User Acceptance Testing (UAT)

Definition Objectives Importance

UAT is the process of UAT aims to validate that UAT is crucial in
testing the software to the final product is ready verifying that the
ensure it meets the for deployment and software functions as
business requirements and meets the stakeholders' intended and is suitable
user needs. expectations. for real-world use.
Planning and Executing UAT
1 Define Test Scenarios
Identify realistic test scenarios that cover the software's
key functionalities.

2 Recruit Test Participants

Carefully select a diverse group of end-users to participate in
the UAT process.

3 Conduct Test Sessions

Facilitate structured UAT sessions, observing user
interactions and gathering feedback.
Examples of Test Case
 Analyzing Test Results*

Aggregate Feedback
▪ Collate and organize the feedback and observations
gathered during the testing sessions.

Identify Patterns
▪ Analyze the data to identify common issues, user pain
points, and areas for improvement.

Prioritize Findings
▪ Prioritize the identified issues based on their severity and
impact on the user experience.

*Include the Testing result in Poster and Final Report.

Field Testing Assessment
 Conclusion and Key Takeaways

1 Embrace User-Centric Testing 2 Iterate and Improve

Prioritize user acceptance testing and Continuously gather feedback and
usability testing to ensure your software implement iterative improvements to
meets user needs. enhance the user experience.

3 Collaborate with Stakeholders 4 Leverage Testing Techniques

Engage with end-users and stakeholders Utilize a variety of testing techniques to
throughout the testing process to align gather comprehensive insights and data-
with their expectations. driven decisions.
 USEFUL LINKS
Institute of Software Testing Qualifications Board
[Link]

ISO/IEEE Standards [Link]

[Link]

QAI Global Institute

[Link]

Wikipedia:
[Link]