eunice0121.com

🧪 QA (Quality Assurance) & QC (Quality Control) Terms I

1. Basic Concepts for Quality Assurance

• QA (Quality Assurance):
  A comprehensive process to ensure that a product or service maintains a certain level of quality.

• QC (Quality Control):
  The process of checking and verifying whether a product meets specified standards.

• Testing:
  The process of executing a system to detect bugs (defects).

• Bug / Defect / Issue:
  An error in software that causes unexpected or incorrect behavior.

• Regression Testing:
  Testing to confirm that existing functionality has not been broken by recent changes.

• Smoke Testing:
  A basic test to check whether the most important functions of a software application work properly.

• Sanity Testing:
  A quick test to verify that a specific feature or bug fix works as expected.

---

2. Types of Testing

• Manual Testing:
  Testing performed manually by a human without automation tools.

• Automated Testing:
  Testing that uses scripts or tools to automatically execute test cases.

• Unit Testing:
  Testing individual units or components of a codebase.

• Integration Testing:
  Testing to ensure that multiple modules or services work together properly.

• System Testing:
  A test to verify that the entire system meets specified requirements.

• User Acceptance Testing (UAT):
  Testing conducted by end users in a real-world environment before final release.

---

3. Testing Methodologies

• Black Box Testing:
  Testing based on inputs and outputs without knowledge of internal code.

• White Box Testing:
  Testing with full knowledge of internal code structures.

• Grey Box Testing:
  A mix of both black box and white box testing approaches.

---

4. QA Documentation and Process

• Test Case:
  A document describing steps and conditions to validate specific functionality.

• Test Plan:
  A document outlining the overall strategy and scope of testing.

• Test Report:
  A summary document of the test results.

• Bug Report:
  A detailed document describing discovered defects/bugs.

---

📘 Explanation of Test Strategy (in the Test Plan)

Test Strategy refers to the overall direction and approach for conducting testing, described within the Test Plan.

🔹 Key Elements

• Test Approach

  • Black Box vs. White Box Testing

  • Manual vs. Automated Testing

  • Functional vs. Non-functional Testing (Performance, Security, etc.)

• Scope and Prioritization

  • Which features to test (e.g., core, new, high-risk)

  • Priority testing for high-risk areas

• Test Environment and Tools

  • Browser, OS, device compatibility

  • Tools like Selenium, JMeter, etc.

• Bug Management and Reporting

  • Tools for tracking and reporting bugs (e.g., JIRA, Trello)

  • Reporting structure after testing is complete

• Schedule and Role Assignment

  • Test milestones and timelines

  • Roles and responsibilities for each team member

---

📘 Overview: Confluence & Atlassian

1️⃣ What is Atlassian?

Atlassian is a global IT company providing collaboration and software development tools.
Popular products: JIRA, Confluence, Trello, Bitbucket
Main users: Developers, project managers, QA engineers, IT teams

2️⃣ What is Confluence?

Confluence is a collaboration and documentation platform developed by Atlassian.
It helps teams create, share, and collaborate on documents.

Main use cases: internal wikis, project documents, technical documents, meeting notes

✅ Key Features of Confluence

• Document creation and management – project plans, meeting notes, technical spec

  

• Real-time collaboration – multiple users can edit simultaneously

• Version control – track changes and revisions

• Integration with JIRA – link dev tasks and project progress

🆚 JIRA vs. Confluence

👉 Summary:
JIRA is for managing development and QA processes.
Confluence is used like a company wiki for documentation and collaboration.

---

📱 What is TestFlight?

TestFlight is Apple’s official beta testing platform for iOS apps.

Supports: iOS, iPadOS, watchOS, macOS, tvOS

Used for:
Distributing apps to testers before App Store release via App Store Connect

✅ Key Features

• Beta testing before official launch

• Invite up to 10,000 testers via email or public link

• Upload and manage multiple app versions

• Collect feedback and bug reports from testers

📌 How to Use (For Developers)

1. Enable TestFlight in App Store Connect

2. Upload the build from Xcode

3. Invite testers (Internal & External)

4. Testers download the app via TestFlight

5. Gather feedback, improve, then release to App Store

🆚 Internal vs. External Testing

---

✅ Summary

TestFlight is Apple’s platform for beta testing iOS apps before official release — essential for QA and feedback collection.

More information on QA/QC…

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