Monday, 30 July 2012

Testing types in CCFD


Integration Testing
Integration testing defects faults that have not been detected.  During unit testing by focusing on small groups on components two or more components are integrated and tested and once tests do not reveal any new faults, additional components are added to the group.  This procedure allows testing of increasing more complex parts on the system while keeping the location of potential faults relatively small.  I have used the following approach to implements and integrated testing.
 Top-down testing strategy unit tests the components of the top layer and then integrated the components of the next layer down.  When all components of the new layer have been tested together, the next layer is selected. This was repeated until all layers are combined and involved in the test. In this project, two or more components are tested together. Here the top down approach is followed.
7.2.3 Validation Testing
            The systems completely assembled as package, the interfacing have been uncovered and corrected, and a final series of software tests are validation testing. The validation testing is nothing but validation success when system functions in a manner that can be reasonably expected by the customer. The system validation had done by series of Black-box test methods.
            In this project, save schedule, generate schedule tests are black box tests.
System Testing
  • System testing ensures that the complete system compiles with the functional requirements and non-functional requirements of the system, the following are some system testing activities.
  • Functional testing finds differences between the functional between the functional requirements and the system. This is a black box testing technique. Test cases are divided from the use case model.
  • Performance testing finds differences between the design and the system the design goals are derived from the functional requirements.
  • Pilot testing the system is installed and used by a selected set of users – users exercise the system as if it had been permanently installed.
  • Acceptance testing, I have followed benchmarks testing in a benchmarks testing the client prepares a set of test cases represent typical conditions under which the system operates. In our project, there are no existing benchmarks. But, there are certain benchmarks available on the Internet regarding the minimum and maximum time limits for generating the random Big Integer values. We have used these to test the system.
  • In this project, all the components are tested together and get the required results

No comments:

Post a Comment