4. Software testing terms
o Test Case: a set of actions performed on a system to
determine if it satisfies software requirements and functions
correctly
o Test Plan: a detailed document that describes the test
strategy, objectives, schedule, estimation, deliverables, and
resources required to perform testing for a software product
o Test Suite: collection of test cases that are intended to be
used to test a software program to show that it has some
specified set of behaviors
o Test Bed: The test execution environment (hardware,
software, OS, network, etc) configured for testing
Introduction
Software Testing
Test Plan
5. Testing terms
o Alpha Testing: internal acceptance testing performed
mainly by the in-house software QA and testing teams
o Beta Testing: the testing carried out by real users in a real
environment. This is the final testing phase where
companies release the software to a few external users
o A/B Testing (not software testing related): experimentation
process wherein two or more versions of a variable (web
page, page element, etc.) are shown to different
segments of website visitors at the same time to
determine which version leaves the maximum impact and
drive business metrics
Introduction
Software Testing
6. Tester’s tasks
ü Review requirements
ü Develop testcases
ü Verify committed tasks, log bugs
ü Retest fixed bugs / reopen bugs
ü Provide test results report
Introduction
Tester’s Tasks
8. 1. What is defect/ bug?
ü A defect is an error or bug in an application that is created during building
or designing software and due to which software starts to show abnormal
behaviors during its use
ü A defect can occur at any point in the software development lifecycle
ü Finding and fixing issues in the early phase saves time, effort, and cost
Defect/ Bug
Definition
9. 2. What causes defect/ bug?
ü unclear requirements
ü programming errors
ü software complexity
ü lack of communication
ü timeline deviation
ü errors in bug tracking
ü documentation errors
ü deviation from standards
and much more
Defect/ Bug
Definition
10. 3. How to identify
ü Sighting: the event that lets you know that the bug exists. It could be a
test failure, a customer report of a problem, a crash, or a hang
ü Symptom: the specific way the program isn't behaving as expected. It is
more specific than the sighting because often when a program first fails,
the person who makes the sighting isn't paying attention to it at a level to
give a clear symptom
ü Reproducer: the set of steps necessary for an arbitrary user to reproduce
the symptom with at least some probability. It can include manual inputs
and settings, data files or database contents, or configuration details
ü Description: the full write up of the bug
Defect/ Bug
Definition
11. 3. How to identify
ü Failure: usually related to the part of the program that is responsible for
doing what the program does when the symptom occurs. Ex: A program
may crash because it dereferences an invalid memory address
ü Cause-Effect Chain: there may be one or more steps of cause and effect
that separate the initial defect in the code from the final failure that lead
to the symptom
ü Defect: the actual mistake in the program itself. It is the cause at the
beginning of the effect chain. Sometimes it is a single line, word, or even
character. Generally, this can only be determined by analyzing the
behavior of the program to find each link in the cause-effect chain
Defect/ Bug
Definition
12. 4. Difference between Error, Defect and Failure
ü Error: If the developers find that there is a mismatch in the actual and expected behavior of an
application in the development phase then they call it an Error.
ü Defect / Bug: If testers find a mismatch in the actual and expected behavior of an application in the
testing phase then they call it a Defect.
ü Failure: If customers or end-users find a mismatch in the actual and expected behavior of an
application in the production phase then they call it a Failure.
Defect/ Bug
Definition
13. Terms Description Raised by
Defect When the application is not working as per the requirement Test engineer
Bug Informal name of defect Test engineer
Error Problem in code leads to the errors Developer, Automation Test Engineer
Issue When the application is not meeting the business requirement Customer, end-user
Mistake Problem in the document is known as a mistake ...
Faillure Lots of defect leads to failure of the software ...
Defect/ Bug
Definition
14. 5. Producible and Non-reproducible defect
ü Producible defect: A defect that is occurring repeatedly in
every execution and can be captured in every execution
ü Non-reproducible defect: A defect that is not occurring
repeatedly in every execution and is producing only at some
instances and whose steps as proof have to be captured with
the help of screenshots
Defect/ Bug
Definition
15. 6. Cost
For an error discovered:
ü In the requirements stage: The cost of the defect is zero
ü In the user acceptance stage: The cost is a lot more expensive
Example: the infamous case of the Samsung Galaxy Note 7
smartphones and all the explosions of the phone...
Defect/ Bug
Definition
16. Defect/ Bug
Bug Life Cycle
Status
New: Bugs created by testers. Developers will not work on these bugs
Approved: Task already reviewed and approved by PM or BA
In Progress: Bug is working / fixing by developers
Committed: Bug already fixed but this is not developed yet
Ready To Verify: Bug already deployed and QC can start testing
Done: Bug already verified successfully
Removed: Bug removed due to some reasons
21. ü Planning
û The list of business processes to be tested is prepared.
û Defining the acceptance criteria.
û Select the testing team.
û Prepare the test data. The test data should cover all the software’s functional scenarios in real-world usage.
û Prepare a UAT test plan. UAT test plan is prepared for the test execution.
ü Design the test: we use the information collected in the planning phase to design the tests.
ü Execution the test using the test data and document the results. Defects found in the system are resolved and re-tested.
ü Confirmation of business objectives
Sign-off: This states that the software product meets the business requirements and is ready for production. The overall
UAT process’s deliverables are Test Plan, UAT scenarios, test cases, test results, and defect log
UAT
Process
23. Web – Textbox verification
Web - Image Upload Verification
Verification
Web Testing
Negative Cases Positive Cases
Leave empty
Out of range (length) - edge of range +-1 In range
Input characters to numeric fields Input number in numeric field
Missing 1 of combined constraints Input character and/or number in character field
Negative Cases Positive Cases
Exceed size (bytes) Within size (bytes)
Exceed size (pixel) Within size (pixel: width and height)
File extension which is not supported Proper extension
Non-image file extension
No image
Same/Different filename
24. Web – Date & Time verification
Web - Dropdown list Verification
Web – Links
ü All menu links
ü All page links
ü Orphan page – Page without any link
Verification
Web Testing
Negative Cases Positive Cases
Leave empty Field "To" >= field "From"
Field "To" < field "From" Input date/time manually or select from the dialog
Select Past Date select near future date
Input just one field (To or From)
If input manually, consider data validation
Negative Cases Positive Cases
Leave empty Pick one from the list
Input data instead of selecting from the list
25. Web – Search function
ü Keywork matches 100% with the result
ü Keywork is part of the result
ü Case sensitive checking: SEArch, Search, search, etc
ü Special characters: *, ~, !, #, $, %, ^, &, etc
ü Empty search
ü Combine with other conditions: AND, OR, NOT
Web – Content verification
ü Spelling
ü UI
ü Response time (pages loading, downloading, etc)
ü Color, font size, etc
ü Web elements (buttons, checkboxes, textboxes, links, etc) present
Verification
Web Testing
26. App – Types of testing
ü Usability testing - Kiểm thử tính khả dụng
ü Compatibility testing - Kiểm thử khả năng tương thích
ü Interface testing - Kiểm thử giao diện
ü Service testing - Kiểm thử chức năng
ü Performance testing - Kiểm thử hiệu suất
ü Operational testing - Kiểm thử khả năng hoạt động
ü Installation testing - Kiểm thử cài đặt
ü Security testing - Kiểm thử bảo mật
App – Common issues
ü App crashes
ü App stops working and hang
ü Cannot perform main flow of a function
Verification
Mobile App Testing
