Acceptance Testing: User acceptance testing (UAT) is one of the final stages of a software project and will often occur before the customer accepts a new system.Users of the system will perform these tests which, ideally, developers have derived from the User Requirements Specification, to which the system should conform.Test designers will draw up a formal test plan and devise a range of severity levels. The focus in this type of testing is less on simple problems (spelling mistakes, cosmetic problems) and show stoppers (major problems like the software crashing, software will not run etc.). Developers should have worked out these issues during unit testing and integration testing. Rather, the focus is on a final verification of the required business function and flow of the system. The test scripts will emulate real-world usage of the system. The idea is that if the software works as intended and without issues during a simulation of normal use, it will work just the same in production.Results of these tests will allow both the customers and the developers to be confident that the system will work as intended.

Read more on What is Acceptance Testing?…

Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team. Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.

Read more on What is integration testing?…

A good code is code that works, is free of bugs and is readable and maintainable. Organizations usually have coding standards all developers should adhere to, but every programmer and software engineer has different ideas about what is best and what are too many or too few rules. We need to keep in mind that excessive use of rules can stifle both productivity and creativity. Peer reviews and code analysis tools can be used to check for problems and enforce standards.

Read more on What is a good code?…

An inspection is a formal meeting, more formalized than a walk-through and typically consists of 3-10 people including a moderator, reader (the author of whatever is being reviewed) and a recorder (to make notes in the document). The subject of the inspection is typically a document, such as a requirements document or a test plan. The purpose of an inspection is to find problems and see what is missing, not to fix anything. The result of the meeting should be documented in a written report. Attendees should prepare for this type of meeting by reading through the document, before the meeting starts; most problems are found during this preparation. Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuring quality, since bug prevention is more cost effective than bug detection.

Read more on What is an inspection?…

A good test engineer has a ˜test to break attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful. Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers point of view, and reduce the learning curve in automated test tool programming. Judgement skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.

Read more on What makes a good Software Test engineer?…

Closed box testing is same as black box testing. Black box testing a type of testing that considers only externally visible behavior. Black box testing considers neither the code itself, nor the œinner workings of the software.

Read more on What is open box and closed box testing?…

Stub testing: In top down approach,a core module is developed.to test that core module, small dummy modules r used.so stubs r small dummy modules that test the core module.

Driver testing: In bottom up approach, small modules r developed.to test them a dummy core module called driver is developed.

Read more on What is the difference between stub testing and driver testing…

The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.

Read more on How do you create a test strategy?…

• Testing is the process of detecting & identifying defects where a defect is any variance between actual & expected results.
• Reporting the above.
• Taking necessary corrective measures.
• Process of executing a program with the intent of finding errors.

Read more on What is Testing?…

White Box Testing

White box testing is based on the knowledge of internal program design and code. It is meant to exercise the items internal coding logic by concentrating on its code statements, branches, paths and conditions.

Read more on What are two principal testing strategies?…

SEI = ˜Software Engineering Institute at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes.

CMM = ˜Capability Maturity Model, now called the CMMI (Capability Maturity Model Integration), developed by the SEI. Its a model of 5 levels of process ˜maturity that determine effectiveness in delivering quality software.
It is geared to large organizations. However, many of the QA processes involved are appropriate to any organization, and if reasonably applied can be helpful.
Organizations can receive CMMI ratings by undergoing assessments by qualified auditors.

Read more on What is SEI? CMM? CMMI? ISO? IEEE? ANSI?…

1. A good tester will always try to reduce the repro steps to the minimal steps to reproduce; this is extremely helpful for the programmer who has to find the bug.

Read more on What are the different ways for Bug Tracking and how to go for it ?…

White Box Testing

White box testing is based on the knowledge of internal program design and code. It is meant to exercise the item’s internal coding logic by concentrating on its code statements, branches, paths and conditions.

Read more on What are two principal testing strategies?…

This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:

Read more on How can it be known when to stop testing?…

Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results. Generally speaking¦

Read more on How do you create a test plan/design?…

First, unit testing has to be completed. Upon completion of unit testing, integration testing begins.
Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team.

Read more on How do you perform integration testing?…

Test Strategy:
It is a company level document and developed by QA category people like QA and PM. This document defines “Testing Approach” to achieve testing objective. Test strategy is the freezed part of BRS from which we get Test Policy and Test Strategy.

Read more on What is the difference between Test Strategy and Test Plan?…

Responsibilities of a Test Manager:

- Manage the Testing Department.
- Allocate resource to projects.
- Review weekly Testers’ status reports and take necessary actions
- Escalate Testers’ issues to the Sr. Management.
- Estimate for testing projects.
- Enforce the adherence to the company’s Quality processes and procedures.
- Decision to procure Software Testing tools for the organization.
- Inter group co-ordination between various departments.
- Provide technical support to the Testing team.
- Continuous monitoring and mentoring of Testing team members.
- Review of test plans and test cases.
- Attend weekly meeting of projects and provide inputs from the Testers’ perspective.
- Immediate notification/escalation of problems to the Sr. Test Manager / Senior Management.
- Ensure processes are followed as laid down.

Read more on What is the role of test manager, test lead or a tester ?…

The Life Cycle of a bug in general context is:

Bugs are usually logged by the development team (While Unit Testing) and also by testers (While sytem or other type of testing).

Read more on What are the different types of Bugs we normally see in any of the Project?…

There are three main terms for testing by simultaneously acting multiple users (real or simulated): load, performance and stress testing.
All performance and stress testing require workload definition as a part of the test. There may be no load, minimal load, normal load, above normal load or extreme load. So we will use the term “load testing” as a general category for all types of testing by simultaneously acting multiple users.

Read more on What are the differences between load, performance and stress testing ?…