Tag Info

New answers tagged

0

We needs to remember two magic words “requirements and specifications” and then approach toaster, vending machine, alarm clock, pen etc etc as any other usual application under test with different testing types like functional testing, usability testing, white box testing, black box testing, performance testing, load testing and so on and so on


0

Testing in debug mode will only let you reliably test truly surface stuff, like UIs. There's so much extra stuff loaded "under the hood" - like stack frame protection - when running in debug, that you're end-stage-loading the testers finding nasty stuff like memory allocation and stack problems (depending on what language you're using). Any formal testing ...


0

Testern should not test in debug mode, but only devs should do this in their development tests. A good testing strategrie provides the following enviroments: Developement enviroment for development tests (with debugmode switchable by the devs for on/off Integration eviroment for the QA to test the software under real conditions - this especially means ...


0

Below are the components of a test plan, which should be included. 1. Summary 1.1. Introduction - Provide an overview of this document in this section 1.2. Scope of testing - The scope of testing needs to be clearly defined. The plan should define items / features that are in scope or out of scope for the testing phase. - 1.2.1. **Features To be tested** ...


2

What are the most important components/parts of a well-written test plan document for a testing project. Consider you are testing a Financial web app. As per IEEE 829 standards, the components of a Test Plan document should be : Test Plan identifier References Introduction Test Items Risks Items to be tested Features excluded for testing Testing ...



Top 50 recent answers are included