Please be careful not to wish for less, otherwise Santa might not bring all you want!
Nowadays a fast ‘time to market’ in combination with high expectations on quality, agility and flexibility is expected from digital companies. This means you need solid but pragmatic software quality strategies.
To ensure all this, your software quality wish list and new year’s resolutions for 2023 should look like this:
Let Santa explain why…
First of all, Santa pleads you to apply a shift-left approach to your development and quality process. In short, this means to start testing as early as possible in the software development life cycle. The goal is to fail fast and adapt quickly. A key-factor in this is test automation.
As you can see our traditional Testing Pyramid is replaced by a Testing Trophy. The Testing Pyramid argues that you should have most testing done as unit tests. The Trophy instead says you should have a relatively small amount of unit tests and focus mostly on integration tests. The terms and definitions about ‘unit testing’ and ‘integration testing’ have always been rather cloudy, hence the evolution of these visualizations. But the core message of both stays the same: getting the best ROI out of testing by putting the right amount of effort on each type of test. In particular the balance between unit/integration and larger-flow (E2E) tests.
We regularly apply this approach with success at our customers (read client case LindaCare).
Secondly, Santa advises you to add (at least) T-shaped test resources to your development team to enable DevQAOps. These testers with multiple technical skills can cater for all your QA needs in the team and will be able to make the bridge towards development in terms of understanding and added value. They have competences such as (test) analysis, continuous test automation (API + UI) for DevOps, and performance and/or security testing basics.
The Bright Academy ensures that our employees are well trained and grow their skills continuously; thanks to bootcamps, swITch learning tracks, and many other courses. All of this is also open for non-Brighters. So if you want your employees to improve their skills, take a look at the website.
Furthermore, our domain managers provide individual support on projects (technical or strategic). Brightest stands for #AimHigh, in other words we will always go the extra mile. Also, we want to be first in adopting new technologies and approaches. This way we can help our customers be winners too!
The third Bright advice is to apply a proper testing (automation) strategy when using low-code/no-code development platforms. These platforms are visual software development environments that allow enterprise developers and citizen developers to drag and drop application components, connect them together and create mobile or web apps.
There are many reasons to use and love low-code development platforms and more and more companies are starting to use them. Although these platforms generally include features that allow for experimenting, prototyping, testing and deployment; don’t make the mistake of assuming that low code means low QA. On the contrary, low code makes QA oversight and engagement with the software delivery process even more important. So, we hope you hear Santa’s advice loud and clear: apply a good (automation) testing strategy when using these platforms
Santa’s fourth advice is to investigate the use of low/no code test automation platforms. Low/or no code test automation is an approach to software testing that requires minimal to no coding. The biggest benefit of these kind of tools is that ‘anyone can test’, so this means there is an opportunity for more intuitive user engagement.
However, coded Test Automation is not going anywhere. Basically, organisations shouldn’t be thinking of codeless tools and traditional automation as an either/or scenario. Codeless test automation tools are great for less-involved scenarios, like smoke tests or certain parts of a regression test suite. Using codeless automation tools in this way, allows test engineers and test automators to focus on higher-priority and more complex test automation.
So, you should balance traditional and codeless test automation. And ideally, manual testing is also used alongside both traditional and codeless test automation solutions (mainly for new features). This to maximize the speed, scale and quality at which software can be delivered to end users.
And finally, Santa’s fifth advice is to never forget about the importance of performance and security testing. In the past, these were both somewhat of an afterthought in software development, taken into consideration during the testing phase. But new methodologies like Agile build ongoing testing into every phase of the software development life cycle, and that includes testing for secure and well performing software development. If you invest in these areas, you will improve software performance and security of course, but also
Our presents for you are