SEF9 - IEEE Software Test Documentation Standards (What and Why)

WRY said, "Test everything. But that is not possible. We can only say that it is error free only against those tests we conducted. We can never say that it is totally error free, absolutely." Think about those "hidden bug" or "schroedinbug".

Ha ha ha. We must document our tests ... what documents and why?

IEEE Standard for Software and System Test Documentation

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=4578383

1.3 Test objectives

Software-based systems are composed of software, hardware, interfaces, and operators/users. Testing processes include the consideration of interactions with all other system components, such as:

Environment
===========================================================
: Determine that the solution represented in the software-based system correctly accounts for all conditions, such as natural phenomena, physical laws of nature, business rules, physical properties, and the full ranges of the system operating environment (as applicable).

Operators/users
===========================================================
: Determine that the software communicates the proper status/condition of the software-based system to the operator/user and correctly processes all operator/user inputs to produce the required results. For incorrect operator/user inputs, ensure that the system is protected from entering into a dangerous or uncontrolled state.

Validate that operator/user policies and procedures (e.g., security, interface protocols, and system assumptions) are consistently applied and used across each component interface. Validate that all forms of user documentation are complete and correct (e.g., error messages, help files, online and offline system support, user guides, and user training materials).

Hardware
===========================================================
: Determine that the software correctly interacts with each hardware interface and provides a controlled system response (i.e., graceful degradation) for hardware faults.

Other software
==========================================================
: Determine that the software interfaces correctly with other software components of the system or other systems in accordance with the requirements, and that errors are not propagated among software components.

See and read the attached PDF document.

--
WASSALAM
wruslan.hahaha

Attachments:
IEEE-Software-Test-Documentation-4578383.pdf

Full Version with Attachments
Return to Software Engineering Fundamentals (SEF9MMUWRY)
Previous Topic: READING => Linux and Supercomputers
Next Topic: 54 About software testing, software errors, testing documents