Testing plays an important role in the software development lifecycle of any business. Unintuitive, bug-ridden software can cause lost sales and market share, and a damaged reputation. But when your customers are in the defense sector, untested software could mean a loss of confidence in vital systems, and ultimately perhaps even loss of life.
Commonly, test team structure depends on the scale, scope, and duration of each project — teams range from as small as two to three testers and as large as several hundred individuals. Smaller projects might be research and development programs that still need to undergo thorough testing. Larger programs demanding extensive teams might include the development of an entire maritime helicopter program comprising very complex systems that need to be continually tested and refined throughout their entire lifecycle.
Defense organizations must adhere to a strict internal and customer software development standards that define high-level processes and rigorous levels of control. Not only around the development and testing of the software but for the associated documentation and traceability of test back throughout the course of software development.
Another limitation that is more acute in this industry is the ability to perform non-intrusive tests without actually affecting that system’s configuration. Support for true, black-box testing is more critical because:
There’s often no alternative, as APIs are hidden or restricted.
There’s often a mix of software and custom hardware in use.
It’s paramount that information presented to humans is correct and clearly readable (not obscured by some other UI popup).
An Eggplant AI accelerator, containing both the model and a skeleton of a relevant Eggplant Functional suite, to model a GIS mapping application, including the ability to draw polygons and read asset data from on-screen.
An Eggplant Network Scenario that emulates the variability of low bandwidth and intermittent communications as individuals move though the environment.