Software Testing and Quality: Formula Sheet

Software Testing and Quality: Formula Sheet

Build a responsible reference sheet of relationships, conditions, units, representations, and decision rules rather than copying unexplained formulas. Develops test design, unit and integration testing, automation, code review, and quality reasoning. Course titles, local sequences, grading, safety rules, required tools, and assessment formats vary; align this resource with the current syllabus and instructor directions.

Learning outcomes

• Explain and apply test cases and oracles, then connect it to unit testing using course-appropriate evidence.
• Explain and apply unit testing, then connect it to integration testing using course-appropriate evidence.
• Explain and apply integration testing, then connect it to property and boundary testing using course-appropriate evidence.
• Explain and apply property and boundary testing, then connect it to quality processes using course-appropriate evidence.
• Explain and apply quality processes, then connect it to test cases and oracles using course-appropriate evidence.

Prerequisite readiness

programming fluency, functions, data structures, and version-control basics Use a short ungraded check, repair the smallest missing skill, and immediately retest it in a course-level task.

Reference-sheet entries

• test cases and oracles: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• unit testing: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• integration testing: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• property and boundary testing: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.
• quality processes: record its governing relationship or decision rule, required conditions, units or evidence, one representation, and a common misuse.

Use test

Can you choose the right relationship on an unlabeled task and explain why its conditions hold? If not, the sheet is storage rather than understanding.

Reliable method

state expected behavior, partition inputs, target boundaries, automate repeatable checks, and investigate failures Keep assumptions, intermediate reasoning, units, sources, tool use, and checks visible so another learner can follow the decision process.

Representative application

Design tests for a date-calculation function, including leap years, invalid dates, boundaries, and invariants. Predict a reasonable result before working, compare the outcome with the prediction, and explain limitations or alternative interpretations.

Error recovery

Watch for measuring quality by test count or code coverage alone without meaningful assertions and risk-based cases. Mark the first unsupported move, classify the cause, correct the reasoning, and schedule a fresh mixed recheck after a delay.

Accessibility, integrity, and safety

Use approved accommodations and accessible formats. Follow course rules for collaboration, citation, calculators, software, generative tools, laboratories, clinical settings, field activity, privacy, copyright, and human or animal subjects. Never use Exams.fit to obtain protected questions or bypass assessment rules.

Evidence to save

When permitted, preserve a test plan, automated suite, defect report, and coverage rationale with the prompt, first attempt, feedback, revision, verification, and reflection. Remove restricted assessment content and private or proprietary information.

Open-learning reference

Compare this original Exams.fit resource with the relevant OpenStax collection and MIT OpenCourseWare when they match the local course. Reviewed August 2, 2026. This page does not replace the current syllabus, instructor, institution, or qualified professional.