Category: Software Testing Basics

  • Test Planning

    Structured handling of a task as extensive as testing will not work without a plan. Test planning begins directly at the start of a software project. Like with any plan, it is necessary to review your testing plan regularly and update or adapt it to fit changing situations and project parameters. Test planning is therefore…

  • The Testing Process

    Development models Introduces different types of software development lifecycle models (also referred to more simply as “development models”). These are designed to aid structuring, planning, and management of new or continuing software projects. In order to perform well-structured tests, you will usually need more than just a description of the activities that make up the…

  • Quality Management and Quality Assurance

    QM Quality management (QM) covers all organizational activities and measures that serve to control quality. Quality management is usually responsible for defining quality policies, quality objectives, quality planning, quality assurance, and quality improvement. This makes quality management a core management activity. Quality management is mandatory in industries such as aviation, automotive, and healthcare. ISO 9000…

  • Applying ISO 25010 to VSR-II

    The VSR-II testing/QA lead suggests using the product quality model described in ISO 25010 to the project steering committee. The committee agrees and asks the testing/QA lead to prepare a concept paper on how to apply the standard in the context of the VSR-II project. The core of the draft is a matrix that illustrates the relevance of each…

  • Software Quality according to ISO 25010

    According to the ISO 25010 standard [ISO 25010], software quality can be classified in two major ways7: The quality in use model comprises the following five characteristics: The product quality model comprises eight characteristics: The product quality model has the most similarities with the previous ISO 9126 standard. Details of the Data Quality Model can be found in the…

  • Software Quality

    Software testing serves to identify and remedy failures and increase software quality. Test cases should be chosen to mirror the subsequent real-world use that the system is designed for. The quality that testing verifies should then equate to the quality of the user experience. However, software quality is about more than just correcting the faults…

  • The Basic Principles of Testing

    The previous sections addressed software testing, whereas the following section summarize the basics of testing in general. These are guidelines that have developed over decades of testing experience.

  • Applying Testing Skills Early Ensures Success

    Testing is an important factor in any success story In software projects, it is never too early to begin preparing your tests. The following examples illustrate the benefits of involving testers with appropriate test knowledge in individual activities within the software development life cycle: Close cooperation between developers and testers throughout the development process In…

  • Risks and losses when failures occur

    The DreamCar module constantly updates and displays the price of the current configuration. Registered customers with validated ID can order a vehicle online. Once a customer clicks the Order button and enters their PIN, the vehicle is ordered and the purchase committed. Once the statutory revocation deadline has passed, the chosen configuration is automatically passed on to the production…

  • When is increased testing effort justifiable?

    Is a high testing effort affordable and justifiable? Jerry Weinberg’s response to this question is: “Compared with what?” [DeMarco 93]. This response points out the risks of using a faulty software system. Risk is calculated from the likelihood of a certain situation arising and the expected costs when it does. Potential faults that are not…