Process Models and Testing Flashcards

Question

What is Release Testing

Answer 1

Releasing testing is the process of testing a particular release of a system that it is intended for use outside of the development team The primary goal of the release testing process is to convince the supplier of the system that it is good enough for use. Release testing has to show that the system delivers its specified functionality, performance and dependability, and that it doesn't fail during normal use. Release testing is a black box testing porcess where tests are only derived from the system specification.

Answer 2

A separate team, that has not been involved in the system development, should be responsible for release testing. System testing by the development team should focus on discovering bugs in the system (defect testing). The objective of release testing is to check that the system meets its requirements and is good enough for external use (validation testing).

Answer 3

Requirements-based testing involves examining each requirement and developing a test or tests for it. Devise scenarios from the requirements and develop tests for these scenarios.

Answer 4

Part of release testing may involve testing the emergent properties of a system, such as performance and reliability. – Tests should reflect the profile of use of the system. – Performance tests usually involve planning a series of tests where the load is steadily increased until the system performance becomes unacceptable. – Stress testing is a form of performance testing where the system is deliberately overloaded to test its failure behavior.

Answer 5

User or customer testing is a stage in the testing process in which users or customers provide input and advice on system testing. User testing is essential, even when comprehensive system and release testing have been carried out. The reason for this is that influences from the user’s working environment have a major effect on the reliability, performance, usability and robustness of a system. These cannot be replicated in a testing environment.

Answer 6

Alpha Testing Users of the software work with the development team to test the software at the developer's site. Beta Testing A release of the software is made available to users to allow them to experiment and to raise problems that they discover with the system developers. Acceptance Testing Customers test a system to decide whether or not it is ready to be accepted from the system developers and deployed in the customer environment. This is primarily for custom systems.

Answer 7

1. Define acceptance criteria 2. Plan acceptance testing 3. Derive acceptance tests 4. Run acceptance tests 5. Negotiate test results 6. Reject/accept system

Answer 8

In agile methods, the user/customer is part of the development team and is responsible for making decisions on the acceptability of the system

Answer 9

Partition Testing is where you identify groups of inputs that have common characteristics and should be processed in the same way. Automated Testing Guideline-based Testing is where you use testing guidelines to choose test cases.

Answer 10

– Choose inputs that force the system to generate all error messages – Design inputs that cause input buffers to overflow – Repeat the same input or series of inputs numerous times – Force invalid outputs to be generated – Force computation results to be too large or too small

Answer 11

Exhaustive system testing is impossible so testing policies which define the required system test coverage may be developed

Answer 12

– All system functions that are accessed through menus should be tested – Combinations of functions (e.g. text formatting) that are accessed through the same menu must be tested – Where user input is provided, all functions must be tested with both correct and incorrect input

Answer 13

- Test-driven development (TDD) is an approach to program development in which you interleave testing and code development - Tests are written before code and ‘passing’ the tests is the critical driver of development - You develop code incrementally, along with a test for that increment. You don’t move on to the next increment until the code that you have developed passes its test.

Answer 14

Start by identifying the increment of functionality that is required. This should normally be small and implementable in a few lines of code. Write a test for this functionality and implement this as an automated test. Run the test, along with all other tests that have been implemented. Initially, you have not implemented the functionality so the new test will fail. Implement the functionality and re-run the test. Once all tests run successfully, you move on to implementing the next chunk of functionality.

Answer 15

Code coverage – Every code segment that you write has at least one associated test, so all code written has at least one test. Regression testing – A regression test suite is developed incrementally as a program is developed. Simplified debugging – When a test fails, it should be obvious where the problem lies. The newly written code needs to be checked and modified. System documentation – The tests themselves are a form of documentation that describe what the code should be doing.

Answer 16

It includes bug severity and bug priority which are decided by the QA Team and PM respectively. Bug Severity 1. Blocker: Impossible to use/test software 2. Critical: Business-critical error 3. Major: Significant error, but limited to a single aspect of the software. 4. Minor: Confusing or undesirable behaviour 5. Low: Types or problems with third-party software. Bug Priority 1. High: Needs to be fixed ASAP. 2. Medium: Error can be fixed during the next sprint. 3, Low: Fix it later or never.