There are considerable take-home lessons to be taken from a software deployment the size of Facebook.
As this article demonstrates, Quality Assurance (QA) and bug testing should occur on two fronts:
- Analysis of the source code; and
- Analysis of the user inputs and interactions with the software.
As a large and experienced provider of enterprise software, Unit4 has considerable experience in providing a stable ERP platform and leveraging known best practices in QA.
Agilyx also adopts this two-pronged approach in its own QA testing. This is particularly relevant where Agilyx, as the implementation and customisation partner, provides customised code solutions to its clients.
This article was particularly interesting, in that it highlights the progression of QA techniques towards an automated system.
It seems not only is software automating business process, but it is automating the very process of software creation itself.
There are two ways of automatically analysing a piece of software in the hunt for bugs, security vulnerabilities, and other potential issues. Static analysis, as the name implies, is only interested in the source code of the program. Dynamic analysis is the opposite: you run the program, feed it a bunch of inputs, and record how it behaves.