QA (Quality Assurance) & QC (Quality Control) Terms IV

QA (Quality Assurance) & QC (Quality Control) Terms IV

✅ What is a Sanity Test? (for Quality Assurance)

A Sanity Test is a quick test to verify that a specific function or feature is working correctly.

🔹 Characteristics of a Sanity Test

✔ Focuses on core functions → Tests specific parts, not the entire system
✔ Quick validation → Rapid check to confirm the build is stable
✔ Part of a regression test → Checks only the essential parts before full testing
✔ Pass/Fail criteria → If no major issues, the process can proceed to the next stage

🔍 Why Sanity Tests are Needed

After a bug fix or new feature implementation, a sanity test ensures the critical areas are functioning properly before conducting a full regression test.
If a sanity test fails, immediate fixes are required without proceeding to further testing.

🔄 Difference Between Sanity Test and Smoke Test

💡 Summary:
A Sanity Test is a quick check performed after bug fixes to verify if key functionalities are working correctly!

✅ What is “Spec-out”?

Spec-out refers to the process of clearly defining and documenting features or requirements (specifications).

🔹 Key Characteristics

✔ Feature Definition → Clearly outline what functionalities are needed
✔ Requirement Documentation → Provide detailed specs for developers, designers, and QA teams
✔ Project Planning → A preparatory step before development, testing, and release

🛠 When to Use Spec-out

1️⃣ Before developing a new feature
→ Organize details of how the feature will be implemented
2️⃣ When improving an existing feature
→ Document updates and changes
3️⃣ For QA and Test Planning
→ Define testing standards before writing test cases

🔄 Spec-out Example

✅ When spec-ing out a login feature:

• Login method: Email/password, social login (Google, Apple)

• Password rules: Minimum 8 characters, must include at least one number

• Failure handling: Limit login after 5 failed attempts for 10 minutes

💡 Summary:
Spec-out is the process of defining and documenting requirements or features in detail! 📄✨

✅ What is “Turn Definition”?

Turn Definition refers to defining the criteria for transitions or change of flow in a QA or software development process.

🔍 Key Concepts in Turn Definition

✔ Transition Criteria → The point where the process moves to the next step due to user actions or system events
✔ Trigger Events → Specific conditions that cause transitions (e.g., button click, page move)
✔ Exception Handling → Handling of errors or exceptions during flow transitions

🛠 Use Case Examples

1️⃣ User Registration Process

• Input user info → Send verification code

• Input code → Complete registration

2️⃣ Payment Process Turn Definition

• Select product → Move to payment page

• Input payment details → Payment completed

🔑 Checklist Example

💡 Summary:
Turn Definition clearly defines the criteria and conditions for transitions in a process!

✅ What is the Prod Environment?

Prod (Production) Environment is the live environment where the product or service is deployed for end-users.

🔑 Key Characteristics

• Accessible and used by real users

• Most stable and verified version of the software

• Requires high service quality and security

• Real-time data and transactions occur

🛠 Components of a Prod Environment

💡 Comparison with Other Environments

🔥 Summary:
Prod Environment is the final stage where the service is deployed and operated for actual users.

✅ What is the Dev Environment?

Dev (Development) Environment is used for developing and initially testing software.

🔑 Key Characteristics

• Developers write and modify code here

• Most flexible environment, high chance of errors

• Used for new feature development and experimental tasks

• Uses mock data instead of real data

🛠 Components of a Dev Environment

💡 Comparison with Other Environments

🔥 Summary:
Dev Environment is a testing space where developers build and experiment with features. 💻✨

📌 More QA/QC Info…

https://eunice0121.com/category/qa_qc/