Difference between revisions of "Testing"
(→Practices) |
(→See also) |
||
Line 31: | Line 31: | ||
*https://www.mindfulqa.com/what-is-manual-testing/ | *https://www.mindfulqa.com/what-is-manual-testing/ | ||
*https://www.mindfulqa.com/qa-vocabulary/ | *https://www.mindfulqa.com/qa-vocabulary/ | ||
+ | *https://www.altexsoft.com/whitepapers/quality-assurance-quality-control-and-testing-the-basics-of-software-quality-management/ | ||
===Related lectures=== | ===Related lectures=== |
Revision as of 00:15, 31 January 2021
Testing is an endeavor undertaken to try out somebody or something to discover, evaluate, and/or measure the one's capacities, characteristics, and/or defects.
Contents
Types
Human vs non-human subject
Test subject, testee, examinee
Human vs machine tester
Intervention vs observation
- Testing. Taking measures to check the performance or reliability of something, especially before putting it into widespread use or practice, or somebody, especially before hiring. Someone who or something that conducts testing is called a tester. Someone who or something that is tested is called a testee. If a testee is a human being, this testing is called human-subject testing. The testing that utilizes one or more artifacts such as a prototype, marketable, or work product is called artifact testing. The testing that utilizes no artifact is called natural testing.
- Verification. Testing a product at a given stage of development to ensure that it meets specifications and requirements. Verification ensures that the solution is developed correctly; it answers the question, "Did we build the system right?" Also see requirements verification.
- Validation. (1) Testing a marketable to ensure that it satisfies its intended use and conforms to its specifications and requirements. Validation ensures that the correct solution has been developed; it answers the question, "Did we build the right system?" Also see requirements validation; (2) Testing a developed product to insure that the created system actually provides the value intended to its stakeholders.
Every separate application should have possibility to testing separately on remote hardware. For that we need
- policy how and where we can get snapshot of application, and how push changes backwards (is inseparable connected with testing process)
- script to install necessary environment for *nix system or list of it
- possibility take snapshot with production base and without
Practices
See also
- https://en.wikipedia.org/wiki/Product_testing
- https://en.wikipedia.org/wiki/Human_subject_research
- https://www.mindfulqa.com/what-is-user-experience/
- https://www.mindfulqa.com/what-is-manual-testing/
- https://www.mindfulqa.com/qa-vocabulary/
- https://www.altexsoft.com/whitepapers/quality-assurance-quality-control-and-testing-the-basics-of-software-quality-management/