Risk-based testing: check your scores against escaped defects
Take a QA lead whose team uses risk-based testing to plan each sprint. Every story gets a risk score, the team tests the high scorers first, and the low scorers…
You have read this

Do you find software testing interesting? Read this article to understand key concepts and software tester skills you will have to develop to determine if it is a good career choice for you.
Software testers play an important role in quality assurance for various companies. If you are pursuing a software testing career, it may be beneficial to acquire excellent computer system analysis skills and knowledge in order for your software under test to run efficiently, effectively, and meet customer expectations. This article provides an introduction to the key concepts a software tester needs to know.
Before we begin, test your knowledge of some key concepts we will introduce in this article. Can you correctly match the following 17 items...
...using the following words and phrases?
Verification, Validation, Fault sensitivity, Branch coverage, System testing, Integration testing, Partition testing, Unit testing, Failure, Functional testing, Fault, Structural testing, Failure rate, Test case, Domain, Mutation testing, Expected results, Fuzzing
Verification: The process of determining whether the products of a given phase of the software development process fulfill the requirements established during the previous phase. This answers the question "Are we building the product right”. The software should conform to its requirements and specifications.
Validation: The process of evaluating software at the end of software development to ensure compliance with intended usage. This answers the question "Are we building the right product”? The software should do what the user wants.

Validation & Verification should be applied at each phase in the software engineering development lifecycle. There are two goals for any verification or validation activity:discover defects and assess whether or not the system is useful and useable in its intended environment.
Correctness attempts to establish that software is error/vulnerability free while testing attempts to find if there are any errors in it. However thorough testing does not demonstrate that a program is error free. Testing, debugging, and the fault removal contribute to increasing confidence in the correct functioning of the software.
Validation testing aims to ensure that the software meets the user needs and requirements. A successful test shows that a use case has been met. Defect testing aims to discover defects/vulnerabilities in the software where its expected behavior differs from the observed (actual) behavior. A successful test exposes a defect/vulnerability in the system.
Static testing is testing without running the program, including software inspections/ audits and some types of static analyses. Static tests are good at finding possible defects / vulnerabilities (i.e., problems that could lead to defects/vulnerabilities). Examples are SPLINT, SSVChecker, and many others.
Dynamic testing is testing by executing the program with real inputs, including traditional software testing approaches and tools. Examples are manual test execution, PITSS, Junit, and many others.
Software Fault is a static defect in the software; a “bug”. The software Failure is the external, observable, behavior that differs from the expected behavior with respect to the requirements or user expectations. If a defect in the code is executed, this may cause a failure, but not necessarily in all circumstances. For example, some defects require very specific inputs or preconditions to trigger a failure, which may occur rarely or never. In addition to failures caused due to defects in the code, failures can also be caused by environmental conditions. For example, radiation, electromagnetic fields, and pollution can cause defects in firmware or influence the execution of software by changing hardware conditions.
Testing is the process of determining if a program has any errors. While debugging is the process to determine the cause, and removal, of an error discovered via testing. Subsequent confirmation testing checks whether the fixes resolved the defects.
A test case is defined as a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.
A test case is therefore made up of a combination of:
Scaffolding is additional program code that is necessary to support software testing (e.g., Junit). A stub simulates the results of a call to a method, database, library, etc. that has yet to be implemented. A test driver simulates a method that calls to a method that is being tested.

"Software Testing Techniques and Tools" by Josh Dehlinger, NSA Funded Curriculum is licensed under CC BY-NC-SA 4.0.
Take a QA lead whose team uses risk-based testing to plan each sprint. Every story gets a risk score, the team tests the high scorers first, and the low scorers…
You have read this