ST-Manual Testing - 3 - Introduction to software Testing

 

 Software Testing - Introduction

What is software Testing ?

Software testing is a process of evaluating a software system or application to determine whether it meets specified requirements and to identify any defects. The purpose is to validate and verify the functionality, performance, and stability of the software before it is released to the end-users.

When do we go for software testing ?

Software testing is typically performed:

1. During the development process, to catch and fix bugs early.
2. Before the release of the software, to ensure its quality and functionality.
3. After the release of the software, to monitor and maintain its performance and identify any issues.

 Why should we do test software ?

Software testing is performed to:

1. Ensure software functionality and quality before release.
2. Find and fix bugs and errors.
3. Verify that the software meets the requirements and specifications.
4. Improve software reliability and performance.
5. Provide confidence to stakeholders and users.
6. Facilitate maintenance and future updates.

 What if we don't test software adequately?

If software is not tested adequately, it can result in:

1. Poor quality and unreliable software.
2. Unsatisfied users and customers.
3. Financial losses due to bug fixes and damage control.
4. Missed deadlines and project delays.
5. Damage to reputation and credibility.
6. Security vulnerabilities and increased risk of data breaches.

 Explain some major software failures inversely proportional in impact due to lack of proper testing?

Here are some examples of major software failures that were inversely proportional in impact due to the lack of proper testing:

1. Knight Capital Group (2012): A lack of proper testing led to a software failure that resulted in the loss of $440 million in just 45 minutes. The software was supposed to execute trades, but instead it placed unintended orders, leading to massive losses.
2. Healthcare.gov (2013): The launch of Healthcare.gov, the website for the Affordable Care Act, was plagued by technical difficulties and user frustration. Poor testing and insufficient attention to detail resulted in the site crashing, slow load times, and a user experience that was far from optimal.
3. Tesla Autopilot (2016): Tesla’s Autopilot system, designed to provide semi-autonomous driving capabilities, was involved in a fatal crash due to a software failure. It was later determined that the software failed to identify a white truck against a bright sky, leading to the collision.
4. Equifax Data Breach (2017): A lack of proper testing led to a vulnerability in Equifax's systems that allowed hackers to access sensitive information, including Social Security numbers and birth dates, of over 140 million people.
5. Facebook Data Scandal (2018): Facebook was hit with a major data scandal when it was revealed that the data of millions of users had been harvested by political consulting firm Cambridge Analytica. It was later determined that the lack of proper testing and security measures led to the data breach.

These examples highlight the importance of proper testing in software development. Thorough testing can help identify potential problems and prevent them from becoming major failures that can cause significant harm and impact.

 How do we do software testing?

Software testing can be performed through various methods, including:

1. Unit Testing: Tests individual components or units of code.
2. Integration Testing: Tests the interaction and communication between different components.
3. System Testing: Tests the entire system to ensure it meets requirements.
4. Acceptance Testing: Tests the software from the end-user's perspective to determine if it is fit for use.
5. Regression Testing: Tests that previously working functionality has not been impacted by recent changes.
6. Performance Testing: Tests the software's performance under different load conditions.
7. Security Testing: Tests the software's security features and resistance to attacks.
8. Usability Testing: Tests the software's ease of use and user experience.

Top of Form

 Software testing in Scrum model ?!

In the Scrum software development model, testing is integrated into the development process as follows:

1. Sprint Planning: Test cases and test strategies are defined and prioritized in this stage.
2. Sprint Development: Developers write code and perform unit testing, while testers perform integration and system testing.
3. Sprint Review: Completed features and functionalities are demonstrated and tested.
4. Sprint Retrospective: Feedback on the testing process and potential improvements are discussed.

When to start testing and when to end testing in Scrum?

In the Scrum software development model, testing starts as soon as the first piece of code is written and ends just before the product is released.

1. Sprint Planning: The testing process begins with the definition and prioritization of test cases and strategies.
2. Sprint Development: Testing continues throughout the development process, with unit testing performed by developers and integration and system testing performed by testers.
3. Sprint Review: Completed features are demonstrated and tested during the Sprint Review.
4. Sprint Retrospective: Feedback on the testing process and potential improvements are discussed during the Sprint Retrospective.

Testing continues until all features have been thoroughly tested and any bugs and issues have been resolved. It is an ongoing process throughout the development cycle to ensure that the software meets the quality and reliability standards required for release.

How much testing is enough in Scrum model ?

The amount of testing in the Scrum software development model is determined by the definition of done (DoD) for each sprint. The DoD is a shared understanding of what constitutes a usable increment of the product and should include testing as an essential component.

In Scrum, enough testing is performed to meet the definition of done for each sprint and ensure that the software is ready for release. This includes testing of individual units, integrated components, and the system. The focus is on testing the highest priority and risk items first, and then proceeding with less critical items.

It is important to note that testing is an ongoing process in Scrum and more testing may be required as new features are added or changes are made. The goal is to continuously improve the quality of the software, while also ensuring that it meets the needs of the stakeholders and end-users.

 Explain a typical software testing life cycle in detail?

The typical software testing life cycle (STLC) is a structured testing process that defines the testing activities to be performed at each stage of the software development process. The STLC typically consists of the following phases:

1. Requirements Analysis: Analyze the software requirements and identify the scope of testing.
2. Test Planning: Define the testing approach, test strategy, and create a test plan.
3. Test Case Development: Develop test cases to validate the requirements and identify potential defects.
4. Test Environment Setup: Prepare the test environment and make sure it is ready for testing.
5. Test Execution: Execute the test cases and document the results.
6. Test Results Analysis: Analyze the test results, identify defects and document them.
7. Defect Tracking and Reporting: Report the defects to the development team, track their status and prioritize their resolution.
8. Test Closure: Document the testing results, analyze the testing process and make improvements for future projects.

This process is iterative and may be performed multiple times during the development cycle, as changes are made and new features are added to the software. The STLC helps ensure that the software is thoroughly tested and meets the quality and reliability standards required for release.

 Share some benefits of doing thorough software testing!

Advantages of doing thorough software testing include:

1. Improving Quality: Testing helps identify and resolve defects and bugs, resulting in a higher quality and more reliable software product.
2. Reducing Risks: Thorough testing helps to identify potential risks and mitigate them before the software is released, reducing the risk of failure and costly downtime.
3. Enhancing User Experience: Testing helps to ensure that the software meets the needs and expectations of the end-users, resulting in a better user experience.
4. Improving Maintainability: Testing helps to identify areas of the software that may be difficult to maintain or upgrade in the future, making it easier to maintain and enhance over time.
5. Increased Confidence: Thorough testing provides confidence in the software's functionality and reliability, reducing the risk of costly bugs and defects.
6. Better Budget Management: Testing helps to identify and resolve issues early in the development cycle, reducing the cost of rework and avoiding last-minute surprises that can impact budget and timeline.
7. Meeting Regulatory Requirements: Thorough testing helps ensure that the software meets regulatory requirements, reducing the risk of legal and financial consequences.

Thorough software testing is critical for ensuring the quality and reliability of software products and reducing the risk of defects and failures.

What is the basic skillset a test engineer needs in scrum ?

A test engineer in a Scrum team needs the following basic skills:

1. Understanding of software testing concepts and methodologies: This includes knowledge of various types of testing such as functional, regression, and performance testing.
2. Knowledge of testing tools and technologies: This includes experience with test automation tools, bug tracking systems, and test management tools.
3. Ability to write and execute test cases: This includes the ability to create test cases that accurately reflect the requirements and identify potential defects.
4. Knowledge of software development life cycle (SDLC): This includes an understanding of the development process and the role of testing in the SDLC.
5. Communication and collaboration skills: Testers need to be able to effectively communicate and collaborate with the development team and stakeholders to identify and resolve defects.
6. Analytical and problem-solving skills: Testers need to be able to analyse and interpret complex information, identify problems, and find solutions.
7. Adaptability and flexibility: Testing in a Scrum environment require the ability to adapt to changing requirements and priorities, and to work effectively in a fast-paced, dynamic environment.

In addition to these basic skills, continuous learning and professional development are important to keep up with the latest tools, techniques, and trends in software testing.