Hey folks, Please find attached file with concept of window application or Desktop application testing concept, how it differ from client server application, what type of testing should be carried out on window application, how to perform it and related checklists etc. hope this will be helpful to newbie of testing in window application. Thanks, Trupti

2. Interoperability Testing

3. Smoke Testing – This testing is a generalized test of the functionality without getting into the core functionality in depth.

4. Sanity testing – Testing used for determining if the application is sane enough to be considered for a Test effort. If application crashes during initial use then the system is considered unstable for further testing and build or application is assigned for Build fix or Application fix.

5. GUI or Interface Testing

6. In software or application, if look and feel is not good then customer will not attract to buy your product or application. In this case your interface must be tested very properly.

7. Checklist for GUI or Interface Testing

8. The entire spell should be correct on interface

9. The entire tab index should be proper

10. All the alignment of label and other fields should be proper

11. All the mandatory fields should mark with astric (*) sign or some mandatory indication should be there

12. All the menu items and buttons should have short cut keys to access it functionality

13. All over application’s CSS and interface design should be same

14. Tool tip of the elements should be proper

15. Unit testing – Unit testing deals with the testing parameters of the program as a independent functional unit.

16. Functional Testing

17. While matter comes to functionality of the application, it must work proper. For selling the application or product also. Think you are going to give demo of your product to client and if it gets crash then think… how shame!!! So in any condition, your functionality should work proper. This type of testing ignores the internal parts of an application and focuses on the output generation matching the requirement. This is a Black-box type testing improvised to cater to the functional requirements of an application

18. Checklist for Functional Testing in Desktop application

19. Check all your buttons should work proper

20. Check all your menu items should work proper along with shortcuts

21. Check database entry if any

22. Check all the business rules

23. Test forms in all pages along with validation, default values, wrong field inputs etc

24. Check print functionality if any

25. Check reports if any

26. Integration testing – This testing cross checks integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

27. Incremental integration testing - This testing adopts the Bottom up approach for testing i.e repetitive testing of an application as enhancement to functionality is done. This testing is mandatory on enhancements and patch applications. Application functionality and modules should be stand-alone to test separately. This testing can be done either by programmers or can be undertaken by testers.

28. System testing – The entire functionality of the system is tested as per the system requirement documents. This is also a Black-box testing that is based on overall requirements specifications, which covers integrated parts of a system.

29. Acceptance testing - Normally this type of testing is done to verify if system meets the customer specified requirements. The End user is the entity who determines the functionality meeting their requirements.

30. Regression testing – This Testing applies to the application in totality for the modification in any part of functionality. Automation tools provide the needed support in this testing as it is difficult for the human tester to cover all aspects of regression

31. Usability testing

32. This is a critical part of testing concentrating on User-friendliness. The Application’s flow is tested on terms of ease of use, help documentation availability at appropriate instances. Basically system navigation is checked in this testing.

33. Checklist for Usability Testing in Desktop application

34. Check all the navigation of the pages should work proper

35. Verify content of the application

36. Verify if any documentation like help file is there then its content

37. Verify easiness of the application with respect to end user

38. Alpha testing – In this testing, an In house virtual user environment is created similar to the implementation environment. This testing is done at the end of the development cycle. Scope for slight design changes exists at this phase of testing

39. Beta testing – This Testing is typically performed by end-users or users outside the purview of the project. This marks the final testing before releasing application for commercial purpose

40. Comparison testing – The product strength in terms of functionality with respect to competitor products and in case of version or release, the comparison to the existing version in terms of change request.

41. Performance testing – Can be subjectively called as load or stress testing depending on the application to be tested. The purpose of this test is to check whether system meets performance requirements.

42. Stress testing - System is stressed beyond its specifications to check the cause and incidence of failure. This testing is performed under heavy load by subjecting the application to huge information beyond storage capacity, performing complex database queries, Rapid and continuous input or requesting heavy retrieval of information from the database.

43. Load testing - It is a type of performance testing to check the system’s behavior under load. The application is subjected to heavy loads to determine the system’s response time and the point of degradation and failure to perform the intended functionality.

44. Security testing – This testing is done to check if the system can be penetrated by any hacking methods. It is the security testing process on the reaction of the system against possible unauthorized internal or external access. The Testing concentrates on the system and the database security against external attacks.