π§ͺ 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:
-
Intent Recognition
-
Understand the userβs goal
-
Example: βI want to book a flightβ β [Booking Intent]
-
-
Slot Identification
-
Identify required information
-
Example:
-
Departure: Seoul
-
Destination: New York
-
Date: March 10
-
-
-
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
Leave a Reply