Static testing
Static testing is necessary for defect detection at the projecting stage and precisely verified tasks for development of program modules and test plan. Thus, immediate performers of software modules will get a minimal but at the same time sufficient package of documents that will let them start the job with minimal time waste on documents study and tasks comprehension. Testers in their turn will get a full test plan, letting them check the program product operation according to a criterion “how it should work”, and not “how it happened to work”, as it often happens.
Economic benefits of static testing are obvious. The majority of major mistakes in program products arise from incomplete lists of demands or incorrect tasks. A developer often receives an insufficient or excessive package of documents. These difficulties will be solved, if static testing is used. It means that the possibility of major mistakes is going down at the development stage. According to various estimations, the costs of error correction at the stage of static testing is 5 times less that at the stage of dynamic testing and 20 times less that at the stage of program product operation. Our team will provide a necessary set of operations for static testing, ensuring high quality of project documents and will reduce to the minimum the possibility of critical errors in ready-made software.
Static testing implies contacts with the customer or with the project prime contractor, i.e. with a person, capable of expressing the task explicitly and of correcting demands, if necessary.
The following should work out requirements for software product: the customer or his/her representative, developers’ team representative, testers’ team representative. At this stage the team of testers controls, that the list of requirements is full and consistent. At the stage of development tasks composition testers together with a leader of developers check, if tasks are full and not excessive.
A test plan for dynamic testing is formed during static testing. At that, it includes control of all requirements to software product, as well as control of checkpoints, defined together with developers, as the choice of endpoints for testing depends on programming tools significantly.
