Following are the 3 main categories of defects:
1) Wrong: If the requirements are implemented incorrectly, then they are stated as Wrong defects.
2) Missing: If the requirement is not done which is given by the customer. If a specification was not implemented, or a requirement of the customer was not noted properly, then it is a missing defect.
3) Extra: If a requirement is not given by the end user and if it is done,then it is called as an extra defect. |
The process of configuration management is the process in which the information which describes an enterprise's computer systems and networks, including all hardware and software components, is to be recorded and updated.
The main advantage of this configuration management is that the entire collection of systems will be reviewed and to make sure that any changes that are done to one system should not affect to any another system.
This can also be called as Unified Configuration Management(UCM) when it is used in software development. With the use of this UCM, developers will keep a track on the source code, documentation, problems, changes requested, and changes made. |
The Tailoring model is the best testing model.
The Tailoring is a process of adaptation of a process model to project-specifications and requirements.
In order to get the project-specific process model, the tailoring process will identify the products which are to be deleted and deletes them, and makes some required modifications in the product flows. |
The impact ratings are of 3 types.They are:
1) Minor: These type of impact ratings does not affect the operations as they have very low impact.
2) Major: These type of impact ratings will affect the operations on a very large scale.
3) Critical: These type of impact ratings are powerful. They may cause the system to a halt and stops the show. |
Types of verification are of 4 types. They are:
1) Inspection: It is the most effective way which is used to find the differences from the actual requirements. While doing system level testing, it does not look into the details of the code.
2) Analysis: In this type, the test item will be conducted with mathematical verification. This includes the estimation of execution times and estimation of system resources.
3) Testing: This type is also called as "White box" or "Logic driven" testing.The test item will trace the input values and check whether they are generating the expected output values or not. The typical techniques include condition testing, loop testing and data flow testing.
4) Demonstration: This can also be called as "Black box" or "Input/Output driven" testing. In this type of verification, at first the input values are given.Then the output values are compared with the expected output values.The typical techniques include error guessing, boundary-value analysis, and equivalence partitioning. |
Unit testing - This testing is used to test a smallest unit of functionality, like a method or a class. These tests are used to focus on a particular feature.
Integration Tests - This type is used to test some units of code which build on unit tests.The difference between integration tests and unit tests is the environment, in which the integration tests will use threads, access the database to ensure that all of the code and the different environment changes will work correctly.
System testing - This testing is done to check whether all the requirements are successfully met or not.
Acceptance testing - This testing is used to check for a particular feature whether it meets the required input given by the end user. |
Test log creates an environment which consists of an integrated management environment where you can create and manage your entire test plan, other than your test cases.
It helps in managing the development life cycle.
It also helps in promoting the reusability of the test cases.
It helps in improving the efficiency.
It also helps in managing xml database.
It helps in documenting both automated and manual tet cases. |
|
In any organization, the requirements are given by the clients. In addition to the client's reqirements, the development team will allo give their suggestions for the best output of the product.
But, maintaining all the requirements and to check whether all the requirements are met or not, is somewhat a time taking process. This problem can be solved by using the Requirements Traceability Matrix.
The requirement tracing is the process of making the document by linking the user requirements and the work process (which includes software requirements,design specifications,software code,test plans) developed to implement and verify those requirements. |
Entry Criteria:
The purpose of this criteria is to check whether the suitable environment is there for supporting the entire test process. In this criteria, the items has to meet the following:
1) The test hardware platforms which are installed should be checked whether they are configured and functioned properly.
2) The standard software tools which includes testing tools also should be checked about their successful installation and proper functionality.
3) The availabity of the documentation and design of the architecture should be done.
4) The test cases and the test plans should be reviewed and also must be signed off.
5) There should be the availability of a seperate QA environment.
Exit Criteria:
The main purpose of this criteria is to check whether the application has been successfully completed before existing the system test stage. The items has to meet the following:
1) Maximum test cases are executed
2) There should be no defects during a time of testing effort
3) Severity issues must be fixed. |
Verification is the process which takes place before the Validation process.
The difference between both the process is as discussed below:
Verification:
The main aim of this process is to ensure whether the product is met with the requirements and the specifications given by the end user or not. Its objective is to check whether the data gathered is used in the right place, and in a right manner or not.
Validation:
This process is mainly to check the product, if it is perfectly working or not for its intended use. It is also used to correct the product's design to meet the requirements. |
Below are the differences between Latent and Masked defects:
Latent Defects: These are the defects which are present in the system. These defects remain for a long time and can also be detected in different versions of the software. It may be detected after the release. The main reason for this defect is because the exact set of conditions haven't met.
For Example: February has 28 days. The system will not recognise the leap year and shows an error for leap year. This defect remains in the system and will be recognised in latent defect.
Masked Defects: The main functionality of these defect is that they will hide the other defects in the system. These defects can be observed in page navigations.
If there is a defect in the current page and it causes problem in moving to another page, then the defects in the next page can't be seen. |
Calibration is a process where a device, or a tool is tested about its working progress. This test will let you know how well the device is working. This calibratrion test is very useful such that every device is tested and it could be known if the device is not working properly. |
A risk is such a circumstance which arices a great loss to any organisation. The risk cannot be removed completely but can be minimized to some extent. A risk generally transforms to risk.
For example, If you are managing the accounts section in your organisation, and you have commited some mistakes and you have done the incorrect tax calculation. It results risk to your organisation.
But, if this defect is controlled, you can atleast minimize the risk.This minimization of the risk can be done by correct software testing. |
Coverage is simply a measurement which gives the information about, how much the test case has been exercised.
The different types of coverage techniques are discussed below:
1) Statement coverage: The main advantage of this statement coverage is to identify which blocks of code has been executed in a method or a class.
2) Decision coverage: This is also known as Branch coverage. There will be two outcomes(True/False) for any of the statements like IF/DO-WHILE/CASE. This technique will ensure the outcome should be executed atleast once.
The formula to calculate decision coverage is:
Decision Coverage=(Number of decision outcomes executed/Total number of decision outcomes)*100%
3) Path coverage: In this technique, the test case is executed atleast once in such a way that every path is executed atleast once including all loop paths taken zero, once, and multipe. |
Let us discuss the differences between Pilot and Beta Testing:
Pilot Testing: It is mainly about the quality.In this type of testing, a group of users will try to test on the system,mainly on its full development to provide a feedback on the quality of the product.The users will also provide the feedback on how the technology is useful,and how well it can be improved.
Beta Testing: It is also based on the quality. This Beta testing is done on the client-side. All the end users test the system and check whether the system meets their requirements or not. |