12. Why Is Software Testing Sometimes Required for Legal Reasons

Security testing is essential for software that processes sensitive data to prevent hackers from entering the system. Static testing involves verification, while dynamic testing also involves validation. [15] One of the advantages of black box technology is that no programming skills are required. Regardless of the biases of the programmers, the tester probably has a different sentence and can highlight different functional areas. On the other hand, it has been said that black box tests are “like walking through a dark maze without a flashlight.” [30] Since they don`t look at the source code, there are situations where a tester writes a lot of test cases to verify something that could have been tested by a single test case, or leaves some parts of the program untested. The robustness of a software component is the extent to which it can function properly in exceptional inputs or stressful environmental conditions. [IEEE90] Robustness testing differs from accuracy testing in that the functional accuracy of the software is not important. It only pays attention to robustness issues such as machine failures, process hangouts, or abnormal terminations. Oracle is relatively simple, so robustness testing can be made more portable and scalable than accuracy testing. This research has recently attracted increasing interest, most of which use commercial operating systems as a target, such as the work in [Koopman97] [Kropp98] [Ghosh98] [Devale99] [Koopman99]. One system-level measure for risk management is the mean time to failure (MTTF). Test data from realistic beta tests is used to determine the average time to system failure.

This data is extrapolated to predict the total and expected availability of the system. Sometimes MTTF is used to measure the mean time to repair (MTTR). This represents the expected time for the system to be repaired and returned to service after an error has been observed. Availability, obtained by calculating MTTF/ (MTTF + MTTR), is the probability that a system is available on demand. While these are reasonable measures to assess quality, they are more commonly used to assess the risk (financial or otherwise) that a failure poses to a customer or, in turn, to the system provider. An interesting approach to limiting test cases is based on whether we can limit testing to the “proximity” of change. (Example: If I put a new radio in my car, do I have to do a full road test to make sure the change was successful?) A new type of regression test theory attempts to identify, through program streams or reverse engineering, where boundaries can be placed around modules and subsystems. These diagrams can determine which tests of the existing suite can show a change in behavior in the new version. The reason test determines whether it makes sense to conduct further testing.

Continuous testing is the process of running automated tests as part of the software deployment pipeline to get immediate feedback on the business risks associated with a release candidate of software. [58] [59] Continuous testing includes validation of functional and non-functional requirements; The scope of testing ranges from validating bottom-up requirements or user narratives to assessing system requirements associated with overall business objectives. [60] [61] [62] This method is based on the analysis of the user`s functional requirements for the software with the following categories: Accuracy is the minimum requirement for the software, the essential objective of the tests. Accuracy testing requires some sort of oracle to distinguish good behavior from bad. The tester may or may not know the internal details of the software module being tested, e.g. control flow, data flow, etc. Therefore, a white box point of view or a black box point of view can be taken in the test software. We must bear in mind that black box and white box ideas are not limited to accuracy testing. Black box tests (also called functional tests) treat the software as a “black box” and examine functionality without knowledge of the internal implementation, without seeing the source code. Testers only know what the software needs to do, not how it does it. [27] Black box testing methods include: equivalence partitioning, limit value analysis, all-pair testing, state transition tables, decision table testing, fuzz testing, model-based testing, use case testing, exploratory testing, and specification-based testing.

[19] [20] [24] While automation can`t replicate everything a human can do (and all the possibilities they envision), it can be very useful for regression testing. However, this requires a well-developed test suite of test scripts to be truly useful. Given all this evidence, it has been suggested that “software inspections can replace testing.” While the benefits of inspections are real, they are not enough to replace testing. Inspections could only replace testing if all information obtained through testing could be obtained by inspection. This is not the case for several reasons. First, tests can identify errors due to complex interactions in large systems (e.g., synchronization/synchronization). Although inspections can detect this event, the likelihood of a person understanding all interfaces and being present at all controls is quite low as systems become more complex. To understand the importance of software testing, let`s look at the following: Reality – During SDLC phases, testing never takes much time.

However, diagnosing and correcting errors identified in proper testing is a time-consuming but productive activity.

This entry was posted in Uncategorized. Bookmark the permalink.