lesson 1 Flashcards
The benefits of good testing include
preventing bugs and software improving performance.
true
is the process of evaluating and verifying that a software product or application does what it’s supposed to do.
software testing
WHY IS SOFTWARE TESTING IMPORTANT?
To identify defects
* To reduce flaws in the component or system
* Increase the overall quality of the system
TRUE
is intended to show that a program does what it is intended to do and to discover program defects before it is put into use.
TESTING
When you test software, you execute a program using artificial data.
TRUE - PROGRAM TESTING
You check the results of the test run for errors, anomalies or
information about the program’s non-functional attributes.
TRUE - PROGRAM TESTING
Can reveal the presence of errors NOT their absence.
TRUE - PROGRAM TESTING
The testing life cycle could be divided into eight stages/testing methodologies:
Defining
1. Requirements review: Proves your requirements are ready to be used
2. Usability tests: Prove users can achieve their goals with the application
Building
3. Unit tests: Prove each component works as intended
4. Integration tests: Prove a subsystem of tested components works together
5. End-to-end (E2E) tests (also called system tests): Prove an entire business process that depends on multiple tested subsystems works
Deploying
6. User acceptance tests (UAT): Prove users can complete business tasks; signal the application is ready to be deployed 7. Smoke test (also called sanity check): Proves the application starts after deployment
8. Regression Test: Proves that older tests still succeed after changes have been made.
TRUE
Proves your requirements are ready to be used
REQUIREMENTS REVIEW - DEFINING
Prove users can achieve their goals with the application
USABILITY TESTS - DEFINING
Prove each component works as intended
UNIT TESTS - BUILDING
Prove a subsystem of tested components works together
INTEGRATION TESTS - BUILDING
Prove an entire business process that depends on multiple tested subsystems works
. End-to-end (E2E) tests (also called system tests) - BUILDING
: Prove users can complete business tasks; signal the application is ready to be deployed
user acceptance tests - DEPLOYING
Proves the application starts after deployment
. Smoke test (also called sanity check) - DEPLOYING
Proves that older tests still succeed after changes have been made.
REGRESSION TEST - DEPLOYING
During the requirements review stage, you identify that a crucial
requirement for the payment gateway integration isn’t clearly defined.
Clarifying this requirement now prevents future delays and confusion
during development.
REQUIREMENTS REVIEW
After the initial development, usability tests reveal that users find it difficult to navigate the checkout process. Based on feedback, the interface is
adjusted to make navigation more intuitive, ensuring users can easily
complete their purchases.
USABILITY TESTS
During the development phase, each individual component such as the
‘Add to Cart’ feature undergoes unit testing. It’s verified in isolation to
ensure it correctly adds items to the user’s cart without errors.
UNIT TESTS
Regression tests are performed to make sure existing features like product search and checkout flow still work as expected, ensuring
changes haven’t introduced new issues
regression tests
Basic functions, like loading the homepage, user login, and browsing products, are quickly checked to ensure the application is stable enough for more thorough testing.
smoke test
involves real users from a pilot group testing the e-commerce
platform to confirm it meets their needs
user acceptance tests
This comprehensive test ensures the entire flow works as intended, mimicking a real user’s experience
e2e
. These tests ensure that these components work together seamlessly, allowing users to
search for an item and add it to their cart without issues.
integration tests
