| Testing:
DBMS/Copy 7.0, DBMS Explorer (Data Base Management System) Client. Salford Systems San Diego, California USA The Problem: Analysis, test-plan design, multilevel product testing and update collaborating with the customer. The Solution: Our test-plan includes the following stage: Acceptance Test Specification Functional System Test Integration test Module Test At present, according to originally designed methodology and standards, our testing department, fulfills the following kinds of testing: Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality. Functional testing - black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This does not mean that the programmers should not check that their code works before releasing it (which of course applies to any stage of testing.) System testing - black-box type testing that is based on overall requirements specifications; covers all combined parts of a system. Planned are the following kinds of testing: White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions. unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses. Incremental integration testing - continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers. Regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing. Acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time. Stress testing - term often used interchangeably with 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc. Performance testing - term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans. Usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers. Install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes. Recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. And others problems, according to customers needs. Configuration and Tools: Hardware: IBM PC; Operating System: Windows operating systems family (95/98, NT/2000) |