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

πŸ§ͺ QA (Quality Assurance) & QC (Quality Control) Terms VI


πŸ“Œ What is “Ad-hoc” in Quality Assurance?

Ad-hoc refers to tasks that are performed spontaneously or temporarily for a specific purpose.

πŸ”‘ Meaning in QA:

  • Unplanned, informal testing methods

  • Used to quickly examine specific features or issues when bugs occur

  • Focused on immediate problem-solving without predefined test cases

πŸ“Œ Usage Examples:

Field Description
QA Testing Quickly reproducing and verifying a bug discovered in an app
Networking Setting up a network on the spot in response to an unexpected issue
Software Adding or fixing features urgently

πŸ’‘ Summary:
Ad-hoc testing is a flexible and immediate approach used to resolve unexpected issues without pre-planning. πŸ”


βœ… What is Regression Testing?

Regression testing ensures that existing features still work correctly after code changes such as updates, bug fixes, or enhancements.

πŸ”‘ Key Characteristics:

  • Validates that new features or fixes don’t break existing functionality

  • Commonly automated

  • Includes testing areas beyond the modified code

  • Aims to recheck for side effects or new bugs

πŸ“Œ Examples:

  • After modifying the login feature, checking whether sign-up and logout still work

  • After improving the payment page, verifying that the cart and order history pages remain functional

🚨 Purpose:
To prevent unintended side effects from code changes.


πŸ“Œ When to Use Each?

Test Type When to Use
Ad-hoc Testing When immediate bug exploration is needed without a script, during critical issues or unexpected behavior, or when discovering edge-case bugs
Regression Testing After adding new features, fixing bugs, or following periodic software updates to ensure stability

πŸ“Œ Summary:

  • Ad-hoc Testing = Spontaneous testing to freely explore and find bugs

  • Regression Testing = Repeated testing to ensure new changes haven’t broken existing features

βœ… Conclusion:
Ad-hoc testing is fast and flexible but lacks structure, while regression testing ensures stability but may require more time. It’s important to choose wisely based on context! πŸš€


βœ… What is Slot-Filling?

Slot-Filling is a technique used in Natural Language Processing (NLP) to automatically extract necessary information (“slots”) from user queries or commands.

πŸ”‘ How Slot-Filling Works:

  1. Intent Recognition

    • Understand the user’s goal

    • Example: β€œI want to book a flight” β†’ [Booking Intent]

  2. Slot Identification

    • Identify required information

    • Example:

      • Departure: Seoul

      • Destination: New York

      • Date: March 10

  3. Slot Filling

    • Extract values from the user’s sentence and populate the slots

πŸ“Œ Example:

User: β€œBook a flight from Seoul to New York on March 10.”

Slot Value
Departure Seoul
Destination New York
Date March 10

πŸš€ Where Slot-Filling Is Used:

  • Chatbots

  • Voice assistants (e.g., Alexa, Siri)

  • Booking/reservation systems

  • Customer support automation

πŸ”‘ Key Points:

  • First, identify the intent

  • Then, extract required slots

  • Ask follow-up questions if information is missing

πŸ’‘ Summary:
Slot-Filling helps conversational AI accurately understand and process user needs by extracting key information automatically.


βœ… What is a Handover?

Handover is the process of transferring responsibilities and context from one person to another to maintain business continuity.

🧩 Key Components:

  • Scope – What’s been done and what’s left

  • Status – Completed vs in-progress vs not started

  • References – Documents, account credentials, tool access

  • Issues/Risks – Expected problems or special instructions

πŸ’‘ Example Scenarios:

  • Transferring QA tasks to another tester

  • A designer handing over a project to another designer

  • A PM resigning and passing data to a successor

πŸ—‚ Related Terms:

  • Work Handover Document – Documentation used in transitions

  • Handover Checklist – Checklist to ensure all items are covered


βœ… What is a Hotfix?

A Hotfix is an urgent patch deployed to quickly fix a critical issue, often outside the regular release schedule. It’s commonly used to resolve serious bugs or security vulnerabilities affecting users.

πŸ”§ When Do You Need a Hotfix?

  • App crashes or failure to launch

  • Potential data loss

  • Security vulnerabilities

  • Core feature failures (e.g., login, payment, form submissions)

πŸ” Hotfix vs Regular Release:

Category Hotfix Regular Release
Purpose Urgent issue fix New features & bug fixes
Speed Very fast On scheduled timeline
Scope Minimal changes Broader updates
Testing Limited Full QA cycle

πŸ’‘ Example:

β€œAfter deployment, the editor isn’t saving content. We need a hotfix ASAP to patch it on the production server.”


βœ… What is an RC Version?

RC (Release Candidate) is the last testing version released before the final version of a product.

πŸ§ͺ Release Flow:
Development β†’ Alpha β†’ Beta β†’ RC β†’ Stable

Version Description
Alpha Early version for internal testing
Beta Includes key features; tested by external users
RC Nearly complete; released for final validation
Stable Official public version

πŸ” RC Version Highlights:

  • No new features added

  • Stability and performance testing

  • Final QA or client validation before launch

  • If no issues, becomes the official release


βœ… What Does β€œRelease” Mean?

Release means officially delivering software or a product to users.

🧩 Examples:

Use Case Explanation
App Launch Uploading an app to the App Store = App release
Website Update Apply changes after development & QA = Release
Versioning β€œv1.2.0 released” = New feature version made available

πŸ“Œ Common Terms Related to Release:

Term Meaning
Release Note Document describing updates, fixes, or features
Release Candidate Final test version before launch
Release Schedule Timeline for deployment

🎯 QA’s Role in a Release:
After QA is completed and PO or client approval is given β†’ The feature is deployed live = Release stage


βœ… What is Migration?

Migration refers to moving existing data or systems to a new environment or system.

🧩 Simplified Definition:
It’s like β€œmoving house” β€” but for data, systems, or platforms.

It’s not just copying data. You need to consider structure, compatibility, and validation.

πŸ“Œ Examples of Migration:

Type Description
DB Migration e.g., MySQL β†’ PostgreSQL
Server Migration On-premise β†’ Cloud (e.g., AWS, Azure)
Service Migration Legacy website β†’ New platform
Format/Data Migration e.g., CSV β†’ JSON

πŸ” In QA, Migration Testing Ensures:

  • No data is lost during transfer

  • Transferred data works correctly with the new system

  • Performance and security remain stable

 

πŸ“Œ More QA/QC Info…

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

Leave a Reply

Your email address will not be published. Required fields are marked *