Dynamic Testing: An Essential Stage In The Software Testing ProcessSoftware development, as you're probably aware of, consists of an entire cycle involving building, testing, building and more testing until the software is complete and has successfully passed every test for quality, performance, security, etc. One phase of the testing, which software engineers use to test the dynamic behavior of the code, is Dynamic software. What this means, in simpler terms, are they test the physical parts of the system that change over time and are not steady and constant. There is a certain code written into the system telling the system how to run. The dynamic software testing determines if the code is correct or has errors. Examples of dynamic behavior would a system that works efficiently with a certain flow of activity. Suddenly, the activity level increases and the performance decreases. Another example would be the process loading quickly until more programs and applications are present, at which time, it would load slower or fail to loan altogether. These are both examples of dynamic behavior, which dynamic software testing is designed to catch. Another function of dynamic testing is to input certain values or data into the software and make sure that the output is what it should be. When they get the output, they compare it with what the outputs should be. In the case of a bug in the system, dynamic testing would be a method of clearing out the bug. Any large exterior problem is usually tested by means of dynamic testing. Dynamic testing is run differently than static testing in that static testing is run without the system being run. Dynamic testing, on the other hand, can only be completed when the software is compiled and running. In the testing called verification and validation, dynamic software testing is the validation part. Validation part is testing to make sure they are making the right product. Different methods of dynamic testing are integration testing, system testing, acceptance testing and unit testing (also parts of the validation process of testing). Unit testing is the testing of each individual unit separately before they are integrated together to make a complete section or component. Once they are a complete component, they go through integrating testing to make sure they still function as a group in the same manner they did as individual small units. System testing is the testing done on the complete system (as part of black box testing) to make sure it has been put together correctly and operates as it should. Acceptance testing is testing done from the manufacturer to get the user to "accept" that the system is as it is supposed to be and that they are satisfied with the overall product, "accept", and acknowledge delivery. Each of these tests contributes to make up what is broadly referred to as dynamic testing. |