Scribd
Upload
22 views4 pages

Chapter 3 5

Chapter 3 focuses on software test management, outlining its importance in ensuring software quality through organized testing activities, planning, execution, and reporting. It details key activities, tools, test strategies, and risk management in testing processes. Chapter 5 discusses software quality assurance, emphasizing metrics, attributes, standards, and the ethical responsibilities of testing professionals to maintain trust and quality.

Uploaded by

dagimnega208
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
22 views4 pages

Chapter 3 5

Chapter 3 focuses on software test management, outlining its importance in ensuring software quality through organized testing activities, planning, execution, and reporting. It details key activities, tools, test strategies, and risk management in testing processes. Chapter 5 discusses software quality assurance, emphasizing metrics, attributes, standards, and the ethical responsibilities of testing professionals to maintain trust and quality.

Uploaded by

dagimnega208
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

Chapter 3: Test Management - Design and Execution

1. Software Test Management

• Definition: Organizes testing activities to ensure software quality.


• Importance:
o Reduces defects in production.
o Meets customer requirements.
o Helps in resource allocation and collaboration.

2. Test Management Process

• Planning Phase: Risk evaluation, test estimation, test planning, and test organization.
• Execution Phase: Monitoring, defect management, test reporting, and analysis.

3. Key Activities in Test Management

• Test Planning: Defines scope, objectives, and strategies.


• Test Designing: Creating test cases.
• Test Execution: Running test cases and validating results.
• Exit Criteria: Checklist to mark completion.
• Test Reporting: Documenting test activities and results.

4. Tools for Test Management

• Popular tools: TestRail, Jira, Zephyr, qTest, TestLink.

5. Test Plan

• Purpose: Guides testing activities, reducing costs by catching defects early.


• Users: Developers, testers, project managers, analysts, compliance teams.
• Key Elements:
o Objectives, scope, methodology, approach, risks, roles, schedules, and defect
logging.

6. Test Strategy

• Definition: Defines testing approach.


• Types:
o Proactive: Testing starts early.
o Reactive: Testing begins after development.
• Considerations: Risk assessment, testing levels, experience, regulatory compliance.

7. Test Case Design Techniques


• Requirement-Based:
o Boundary Value Analysis: Focuses on edge values.
o Equivalence Partitioning: Groups similar inputs.
o Decision Table: Tests multiple input combinations.
o State Transition: Tests state changes in software.
o Use Case Testing: Ensures software functions as per user scenarios.
• Structure-Based (White Box Testing):
o Statement Coverage: Every line is tested.
o Decision Coverage: All outcomes are verified.
o Condition Coverage: Each condition is tested.
o Path Testing: Ensures all execution paths are covered.
• Experience-Based:
o Error Guessing: Based on intuition and past defects.
o Exploratory Testing: Performed without predefined cases.

8. Test Data Generation

• Methods:
o Manual data generation.
o Automated tools for faster, error-free data creation.
o SQL injection for backend testing.
o Third-party tools for specialized datasets.

9. Test Environment

• Elements: Software, hardware, networks.


• Factors to Consider: Backup, network settings, OS, databases, browser compatibility.

10. Test Documentation

• Types:
o Test scenario, test cases, test plan, requirement traceability matrix (RTM), test
strategy, bug report, execution report.
• Bug Reporting:
o Clear defect description, reproduction steps, expected vs. actual behavior, severity
levels.

11. Test Reporting

• Types:
1. Test Incident Report: Documents defects.
2. Test Cycle Report: Summarizes activities per cycle.
3. Test Summary Report: Assesses release readiness.

12. Risk in Testing


• Types:
o Schedule Risks: Delays due to poor planning.
o Budget Risks: Overruns due to mismanagement.
o Operational Risks: Resource shortages, poor task allocation.
o Technical Risks: Deficiencies in software design.
o Security Risks: Vulnerabilities affecting data safety.
o Market Risks: Changes in user needs or competition.

Chapter 5: Software Quality Assurance


1. Software Quality Metrics

• Purpose: Evaluate performance, security, usability, and maintainability.


• Types:
o Product Metrics: Assess software quality.
o Process Metrics: Track development efficiency.
• Benefits:
o Improves user experience.
o Reduces costs.
o Ensures regulatory compliance.

2. Key Software Quality Metrics

• Usability: Measured via user satisfaction scores and error rates.


• Customer Satisfaction:
o Net Promoter Score (NPS): Measures willingness to recommend.
o Support tickets: Tracks user complaints.
• Best Practices:
o Use real-time monitoring.
o Combine metrics with feedback.
o Choose metrics relevant to the project type.

3. Software Quality Attributes

• Categories:
o Reliability: System uptime and fault tolerance.
o Maintainability: Ease of updates and modifications.
o Usability: How user-friendly the software is.
o Portability: Compatibility across platforms.
o Correctness: Adherence to requirements.
o Efficiency: Speed and resource usage.
o Security: Protection against threats.
o Scalability: Ability to handle increased demand.
o Interoperability: Communication between different systems.

4. Software Quality Standards

• ISO Standards:
o ISO/IEC 25010: Defines quality characteristics.
o ISO 9001: Ensures quality management.
o ISO/IEC 27001: Focuses on information security.
• IEEE Standards:
o IEEE 730: Quality assurance planning.
o IEEE 829: Test documentation.
• CMMI: Process improvement model.
• Six Sigma: Reduces defects.

5. Professional and Ethical Responsibilities in Testing

• Importance:
o Builds trust among stakeholders.
o Ensures high-quality, risk-free products.
• Ethical Principles:
o Integrity: Report results honestly.
o Objectivity: Avoid biases.
o Confidentiality: Protect sensitive data.
o Accountability: Own testing decisions.
• Challenges:
o Pressure to manipulate results.
o Skipping critical testing due to deadlines.
o Handling sensitive data securely.
• Consequences of Unethical Behavior:
o Legal action.
o Loss of credibility.
o Harm to users.

You might also like