What is a test plan document?
A test plan is a document detailing a systematic approach to testing a system such as a machine or software. The plan typically contains a detailed understanding of the eventual workflow.
The pre-requisite for a test plan are approved BRD (Business requirement) and SRS (Functional requirement)
Once approved BRD is available we will create a draft version of test plan and take Feature scope as an input from BRD in the test plan.
Once the SRS is created we will take applicable test types as an input which will go to test approach section of the test plan. we will also update the test plan for any changes to feature's scope, this may happen during SRS preparation where some of the business requirement may not be feasible to implement in the release
A Project plan to define the Schedule, Roles & Responsibilities
Organization's test strategy document are also require to define Test tools, defect management tools, Risk & Risk Management
What is the difference between test strategy and test approachWhat is the difference between web applications and client server application
What is the difference between business logic and application server
What are web services and how are they tested?
A Web Service is a method of communication between two electronic devices over a network.
Web Services: What all do we need to test?
- Functionality: We need to look for the following in the midst of functional testing
- Specification Review (SR)
- Test Case Development (TCD)
- Test Execution, examination of requests & responses
- Performance: Testing web services performance may be complicated. To avoid this, following a simple rule of clearly mentioning the thresholds upfront, solves problems. Another key is to know the performance requirements in the most accurate manner.
For e.g.
- A good requirement: This service has been identified as serving 50,000 concurrent users with 10 second average response time
- A bad requirement: This service should serve > 4000 concurrent users, and the response should be fast
- Security: Web Services are wide-open in a network. This element opens up a host of vulnerabilities, such as penetration, Denial-of-Service (DOS) attacks, and great volumes of spam data, etc. Distinctive security policies have to be imposed at the network level to create a sound Service Oriented Architecture (SOA). There are certain security policies which are enforced during data transfer, and user tokens or certificates are common sights where data is protected with a password. Precise test cases aimed at directing these policies need to be designed to completely test the Web service security
- Compliance: Compliance testing is required to ensure that:
- Web services meet certain specified standards
- Authorize SOAP request/response messages
- Authenticate WSDL definitions
Difference between Test Plan and Test Stratgey
Test Strategy: Usually describes the generic test approach an organization follows irrespective of any project. It's expected to be a one-time organization level document
Test Plan: Test Plan is more PROJECT specific. It keeps changing from project to project based on it's scope. & Test Strategy section which we include as part of Test Plan is the test approach we follow/define for that specific project.
How do you relate SDLC to STLC
SDLC- SDLC is Software Development LifeCycle, it is a systematic approach to develop a software.
STLC- The process of testing a software in a well planned and systematic way is known as software testing life cycle (STLC).
| S. No. | Phase | SDLC - Software Development Life cycle | STLC - Software Test Life Cycle |
| 1 | Requirements Gathering | Requirements gathering is done by business analyst. Development team analyze the requirements from the design, architecture & coding perspective. | Testing team also review & analyze the requirements. Testing team identifies the testing requirements like what types of testing will be required and review the requirements for logical functional relationship between various features / modules, so that any gaps can be caught at an early stage. |
| 2 | Design | Technical architect works for the high level & low design of the software. Business analyst works for the UI design of the application | Here, test architect generally the test lead/manager, does the test planning, identify high level testing points. Basically, requirement detailing is done in this phase. |
| 3 | Coding or development | Development team does the actual coding based on the designed architecture. | Testing team write the detailed test cases. |
| 4 | Testing | In SDLC, actual testing is carried out in this phase. It includes unit testing, integration testing & system testing etc.. | Test Execution and bug reporting, manual testing, automation testing is done, defects found are reported. Re-testing and regression testing is also done in this phase. But, I don't agree with this statement. So, if I want to relate the testing phase with STLC, I would say it it is testing of test cases & test plans i.e. is basically review of test cases, test scenarios etc.. Preparing test data and test automation |
| 5 | Deployment | Application is deployed on production environment for real end users. | Final testing and implementation is done is this phase and final test report is prepared. For this statement as well, I don't agree. For software / application deployment is basically, when it is installed for real use. So, this way, STLC, deployment would be when test when test cases getting used i.e. execution of test cases. |
| 6 | Maintenance | Basically, it includes, post production / deployment support & enhancements. | Most of people say - Maintenance testing is carried out in this phase.My definition for this is - updation & maintenance of test plans, test case required for the testing of support requests & enhancements as a part of maintenance. |
Difference between software validation and verification
software validation ensures that the product actually meets the user's needs, and that the specifications were correct in the first place, Software validation ensures that "you built the right thing"
software verification is ensuring that the product has been built according to the requirements and design specifications. Software verification ensures that "you built it right"
No comments:
Post a Comment