-
Before the start of any test activity, scope of the testing should be known. You must think hard about it.
- The components of the system to be tested (hardware, software, middleware, etc.) are defined as “in scope“
- The components of the system that will not be tested also need to be clearly defined as being “out of scope.”
Defining the scope of your testing project is very important for all stakeholders. A precise scope helps you
- Give everyone a confidence & accurate information of the testing you are doing
- All project members will have a clear understanding about what is tested and what is not
How do you determine scope your project?
To determine scope, you must –
- Precise customer requirement
- Project Budget
- Product Specification
- Skills & talent of your test team
Now should clearly define the “in scope” and “out of scope” of the testing.
- As the software requirement specs, the project Guru99 Bank only focus on testing all the functions and external interface of website Guru99 Bank (in scope testing)
- Non-functional testing such as stress, performance or logical database currently will not be tested. (out of scope)
Leave a Reply
You must be logged in to post a comment.