In general, a stakeholder is someone who has an interest or is concerned with the outcome of the project or activity or decision. This could be an individual, a group or an organization. Stakeholders can impact and / or be impacted by the outcome of the project. Test Managers must be able to identify software testing stakeholders and manage … Read more
Requirement gathering and management – While determining test scope and estimating test efforts, the Test Manager should also be aware changes in requirements later into the project, undertaking control activities to incorporate the changes in testing as well. It is advisable to make Technical Test Analysts and Test Analysts a part of the requirement reviews. Project Management – … Read more
In very simple terms, test planning refers to planning the activities that must be performed during testing in order to achieve the objectives of the test. Test planning for every test level of the project begins at the starting of that level’s testing process and goes on upto the end of closing activities of the level. Planning, … Read more
Testing is a process rather than a single activity. This process starts from test planning then designing test cases, preparing for execution and evaluating status till the test closure. So, we can divide the activities within the fundamental test process into the following basic steps: 1) Planning and Control: Test planning has following major tasks: i. To determine the … Read more
It saves lots of time and effort because Sanity testing is focused on one or few areas of functionality There is no effort put in towards it’s documentation because it’s usually unscripted It helps in identifying the dependent missing objects. It is used to verify that a small functionality of the application is still working … Read more
Sanity testing is usually performed when any minor bug is fixed or when there is a small change in the functionality. It is a kind of software testing which is done by the testers to ensure that the functionality is working as expected. Sanity testing is narrow and deep. Unlike Smoke testing, Sanity testing is focused on one or two … Read more
Smoke testing does not cover the detailed testing. It’s a non-exhaustive testing with small number of test cases because of which we not are able to find the other critical issues.
It helps in finding the bugs in the early stage of testing. It helps in finding the issues that got introduced by the integration of components. It helps in verifying the issues fixed in the previous build are NOT impacting the major functionalities of the application. Very limited number of test cases is required to … Read more
Smoke testing is a type of software testing which ensures that the major functionalities of the application are working fine. This testing is also known as ‘Build Verification testing’. It is a non-exhaustive testing with very limited test cases to ensure that the important features are working fine and we are good to proceed with the detailed testing. … Read more
There are seven principles of software testing. They are as follows: 1) Testing shows presence of defects: Testing can show the defects are present, but cannot prove that there are no defects. Even after testing the application or product thoroughly we cannot say that the product is 100% defect free. Testing always reduces the number of undiscovered defects remaining in … Read more