1. What is the purpose of the testing?
Software testing is the process used to help identify the
- Correctness,
- Completeness,
- Security, and
- Quality
Software Testing is the process of executing a program or system with the intent of finding errors.
2. What is quality assurance?
Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented towards 'prevention'.
3. What is the difference between QA and testing?
Testing involves operation of a system or application under controlled conditions and evaluating the results. It is oriented towards 'detection'.
Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented towards 'prevention'.
4. Describe the Software Development Life Cycle
It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.
5. What are SDLC and STLC and the different phases of both?
SDLC - Software Development Life Cycle
- Requirement phase
- Design phase (High Level Design, Detailed Level Design i.e., Program specifications)
- Coding
- Testing
- Release
- Maintenance
- System Study
- Test planning
- Writing Test case or scripts
- Review the test case
- Executing test case
- Bug tracking
- Report the defect
A Test Bed is an execution environment configured for software testing. so that it does not interfere with any existing application. It consists of specific hardware, network topology, Operating System, configuration of the product to be under test, system software, and other applications. The Test Plan for a project should be developed from the test beds to be used.
A test bed can be, and often is, destroyed and rebuilt in order to totally eliminate a previous version of the application under test. Virtual PCs are often used as Test Beds because they are easily created and destroyed, without affecting the host hardware or software.
7. What is Test data?
Test Data is data that is run through a computer program to test the software. Test data can be used to test the compliance with effective controls in the software. Test data is often designed to test the limits of the application. For example, if the application expects an account number with 8 digits, the test data might include:
- a valid 8-digit account number
- zero
- blanks
- negative numbers
- a 9 digit number
- a 7 digit number
Miscommunication or no communication about the details of what an application should or shouldn't do can cause the programmers to write faulty code.
Programming errors - in some cases the programmers can make mistakes in logic that seemed reasonable at the time the program was written, but turned out to be faulty in execution..
Changing requirements - there are chances of the end-user not understanding the effects of changes, or may understand and request them anyway to redesign, causing rescheduling of engineers, effects on other projects, and work already completed may have to be redone or thrown out.
Time force - preparation of software projects is difficult at best, often requiring a lot of guesswork. When deadlines are given and the crisis comes, mistakes will be made.
9. What is the Difference between Bug, Error, and Defect?
Error: It is the Deviation from actual and the expected value.
Bug: It is found in the development environment before the product is shipped to the respective customer.
Defect: It is found in the product itself after it is shipped to the respective customer.
10. What is the difference between validation and verification
Verification is done by frequent evaluation and meetings to appraise the documents, policy, code, requirements, and specifications. This is done with checklists, code walk-throughs, and inspection meetings.
Validation is done during actual testing and it takes place after all the verifications have been done.
11. What is the difference between structural and functional testing?
Structural testing is a "white box" testing and it is based on the algorithm or code. The tester knows how the application works internally.
Functional testing is a "black box" (behavioral) testing where the tester verifies the functional specification. The tester does not know how the application works internally.
12. What is the difference between bottom-up and top-down approaches
Bottom-up approach: In this approach, testing is conducted from sub-module to main module. If the higher-level modules are not yet developed, a temporary program is used to simulate that module. These dummy modules are often called Drivers.
Top-down approach: In this approach, testing is conducted from main module to sub-module. If the sub module is not developed, a temporary program, often called a Stub, is used to simulate the sub-module. Quite often a stub will set a constant into a variable rather than actually performing its function.
13. What is Re-test? What is Regression Testing?
Re-test - Retesting means we are testing only the certain part of an application again and not considering how it will affect any other parts or the whole application.
Regression Testing - Testing the application after a change in a module or part of the application to verify that the code change will not adversely affect the rest of the application.
14. What is the difference between Load Testing, Performance Testing, and Stress Testing
Load Testing and Performance Testing are commonly said to be positive testing whereas Stress Testing is said to be negative testing.
Say, for example, there is a application which can handle 25 simultaneous user logins at a time. In load testing, we will test the application for 25 users and check how the application is working in this stage; in performance testing, we will concentrate on the time taken to perform the operation. In stress testing. we will test with more users than 25 and the test will continue to any number and we will check where the application is cracking.
15. What is User Acceptance Testing?
User Acceptance Testing (UAT) - is carried out from the user perspective and it is usually done before the release. The testers are from the client organization (the people who will be actually using the new software) and are not programmers.
-----------------------------------
For more FAQs in Software Testing visit : http://softwaretestingguide.blogspot.com
For more information on Software Testing visit http://www.qa-software-testing.com
No comments:
Post a Comment