- What is user acceptance testing?
- What is manual testing and what is automated testing?
- What are the entrance and exit criteria in the system test?
- If there are no requirements, how will you write your test plan?
- What is smoke testing?
- What is soak testing?
- What is a pre-condition data?
- What are the different documents in QA?
- How do you rate yourself in software testing
- What are the best web sites that you frequently visit to upgrade your QA skills?
- Is defect resolution a technical skill or interpersonal skill from QA view point?
- What is End to End business logic testing?
- What is an equivalence class?
It is also called as Beta Testing. Once System Testing is done and the system seems stable to the developers and testers, system engineers usually invite the end users of the software to see if they like the software. If the users like the software the way it is then software will be delivered to the user. Otherwise necessary changes will be made to the software and software will pass through all phases of testing again.
Manual testing involves testing of software application by manually performing the actions on the AUT based on test plans.
Automated testing involves testing of a software application by performing the actions on the AUT by using automated testing tool (such as WinRunner, LoadRunner) based on test plans
Automated testing involves testing of a software application by performing the actions on the AUT by using automated testing tool (such as WinRunner, LoadRunner) based on test plans
Entrance and exit criteria of each testing phase is written in the master test plan.
Enterence Criteria:
- Integration exit criteria have been successfully met.
- All installation documents are completed.
- All shippable software has been successfully built
- Syate, test plan is baselined by completing the walkthrough of the test plan.
- Test environment should be setup.
- All severity 1 MR’s of integration test phase should be closed.
Exit Criteria:
- All the test cases in the test plan should be executed.
- All MR’s/defects are either closed or deferred.
- Regression testing cycle should be executed after closing the MR’s.
- All documents are reviewed, finilized and signed-off.
Enterence Criteria:
- Integration exit criteria have been successfully met.
- All installation documents are completed.
- All shippable software has been successfully built
- Syate, test plan is baselined by completing the walkthrough of the test plan.
- Test environment should be setup.
- All severity 1 MR’s of integration test phase should be closed.
Exit Criteria:
- All the test cases in the test plan should be executed.
- All MR’s/defects are either closed or deferred.
- Regression testing cycle should be executed after closing the MR’s.
- All documents are reviewed, finilized and signed-off.
If there are no requirements we try to gather as much details as possible from:
· Business Analysts
· Developers (If accessible)
· Previous Version documentation (if any)
· Stake holders (If accessible)
· Prototypes.
· Business Analysts
· Developers (If accessible)
· Previous Version documentation (if any)
· Stake holders (If accessible)
· Prototypes.
The smoke test should exercise the entire system from end to end. It does not have to be exhaustive, but it should be capable of exposing major problems. The smoke test should be thorough enough that if the build passes, you can assume that it is stable enough to be tested more thoroughly.
The daily build has little value without the smoke test. The smoke test is the sentry that guards against deteriorating product quality and creeping integration problems. Without it, the daily build becomes just a time-wasting exercise in ensuring that you have a clean compile every day.
The smoke test must evolve as the system evolves. At first, the smoke test will probably test something simple, such as whether the system can say, "Hello, World." As the system develops, the smoke test will become more thorough. The first test might take a matter of seconds to run; as the system grows, the smoke test can grow to 30 minutes, an hour, or more.
The daily build has little value without the smoke test. The smoke test is the sentry that guards against deteriorating product quality and creeping integration problems. Without it, the daily build becomes just a time-wasting exercise in ensuring that you have a clean compile every day.
The smoke test must evolve as the system evolves. At first, the smoke test will probably test something simple, such as whether the system can say, "Hello, World." As the system develops, the smoke test will become more thorough. The first test might take a matter of seconds to run; as the system grows, the smoke test can grow to 30 minutes, an hour, or more.
The software system will be run for a total of 14 hours continuously. If the system is a control system, it will be used to continuously move each of the instrument mechanisms during this time. Any other system will be expected to perform its intended function continuously during this period. The software system must not fail during this period.
Data required to setup in the system before the test execution.
Requirements Document, Test Plan, Test cases, Test Metrics, Task Distribution Diagrams ( Performance), Transaction Mix, User Profiles, Test Log, Test Incident Report, Test Summary Report
excellent
It is a combination of both , because it deals with the interaction with developer either directly or indirectly which needs interpersonal skills and is also based on the skills of the QA personnel to provide a detailed proof to the developer like snap shots and system resource utilization and some suggestions which are little bit technical.
Testing the integration of all the modules of the AUT.
A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification
Không có nhận xét nào:
Đăng nhận xét