Scribd
Upload
6 views4 pages

Summary in Sqa

The document outlines key concepts and techniques in Software Quality Assurance, covering basics of software testing, types of testing, performance and security considerations, test strategy and planning, and defect management processes. It includes definitions, advantages, and methodologies for various testing types, as well as guidelines for effective test planning and defect reporting. Additionally, it emphasizes the importance of verification, validation, and the use of automation tools in enhancing testing efficiency.

Uploaded by

XO Om XO
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views4 pages

Summary in Sqa

The document outlines key concepts and techniques in Software Quality Assurance, covering basics of software testing, types of testing, performance and security considerations, test strategy and planning, and defect management processes. It includes definitions, advantages, and methodologies for various testing types, as well as guidelines for effective test planning and defect reporting. Additionally, it emphasizes the importance of verification, validation, and the use of automation tools in enhancing testing efficiency.

Uploaded by

XO Om XO
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Here's a summary of answers for your Software Quality Assurance (U64B6SQA) assignment:

Unit 1: Basics of Software Testing

1. Software Testing: Process of evaluating software to detect differences between given


and expected outputs.
Advantages: Detects bugs early, ensures quality, improves performance, increases
customer satisfaction.
2. Fundamental Principles:
o Testing shows presence of defects
o Exhaustive testing is impossible
o Early testing saves cost
o Defect clustering
o Pesticide paradox
o Testing is context-dependent
o Absence-of-errors fallacy
3. Verification vs Validation:
o Verification: Checks if software meets specifications (done during development).
o Validation: Ensures software meets user requirements (done after development).
4. Static vs Dynamic Testing:
o Static: No code execution (reviews, walkthroughs).
o Dynamic: Code is executed to check behavior.
5. SDLC vs STLC:
o SDLC: Software Development Life Cycle – covers entire development.
o STLC: Software Testing Life Cycle – focuses on testing stages only.
6. V-Model: Development and testing happen in parallel. Each development phase has a
corresponding test phase.
(Include a V-shaped diagram with stages like Requirements ↔ UAT, Design ↔
Integration Testing, Coding ↔ Unit Testing)
7. Prioritization Techniques:
o Risk-based
o Business value-based
o Frequency of use
o Customer priority
8. Requirement Traceability Matrix (RTM): Maps requirements to test cases to ensure
coverage and traceability.
9. Software Testing Life Cycle (STLC):
o Requirement Analysis
o Test Planning
o Test Case Design
o Environment Setup
o Test Execution
o Test Closure
Unit 2: Testing Types and Techniques

10. White Box vs Black Box Testing:


o White Box: Tests internal code structure.
o Black Box: Tests functionality without looking at internal code.
11. Levels of Testing:
o Unit, Integration, System, Acceptance Testing
12. Functional Testing: Verifies specific actions/functions of the software.
13. Non-Functional Testing: Tests performance, usability, security, etc.
14. Functional vs Non-Functional:
o Functional: What the system does
o Non-Functional: How the system behaves
15. Form vs Field Level Validation:
o Form-level: Checks overall form submission rules
o Field-level: Validates individual input fields
16. Alpha vs Beta Testing:
o Alpha: Done by internal team
o Beta: Done by end-users in a real environment

Unit 3: Performance and Security

1. Performance Testing: Checks responsiveness, stability under load.


o Types: Load, Stress, Endurance, Spike, Volume Testing
2. Common Performance Problems:
o Memory leaks, slow response, bottlenecks
3. Volume vs Load vs Stress Testing:
o Volume: Large data
o Load: Expected user load
o Stress: Beyond limits
4. Need for UAT: Ensures software meets business needs before launch.
5. How to do UAT: Prepare test cases → Select testers → Execute tests → Fix issues →
Sign-off
6. Security Testing Types:
o Vulnerability scanning
o Penetration testing
o Risk assessment
o Security auditing
o Ethical hacking

Unit 4: Test Strategy and Planning


7. Testing Guidelines: Define process, quality goals, documentation standards.
8. Test Strategy Document Components:
o Scope, objectives, test types, resources, tools, risks
9. Test Planning: Defines objectives, schedule, resources, deliverables
10. Test Design:

 Creating test cases/scripts


 Categories: Specification-based, structure-based, experience-based

11. Test Automation: Use of tools to run tests automatically.


12. Advantages of Automation Tools:

 Faster execution
 Reusability
 Accuracy
 Cost-effective in long term

Unit 5: Defect and Metrics

13. Defect Management Process:

 Detect → Log → Fix → Retest → Close

14. Bug Life Cycle:

 New → Assigned → In Progress → Fixed → Retested → Closed

15. Advantages of Good Defect Report:

 Faster fixing
 Clear communication
 Accurate tracking

16. Defect Report Template:

 ID, title, description, steps to reproduce, severity, status, screenshots

17. Defect Prevention:

 Reviews, standards, training, root cause analysis

18. Test Matrix & Measurements:

 Matrix maps tests to requirements.


 Measurements: Test coverage, defect density, pass/fail rate

Would you like these answers formatted in a printable document (PDF or Word)?

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy