2024-05-02 –, Legends Room
Testing is an integral part of any software development process, including DevOps. Most DevOps processes have a bucket of functional tests which are run as part of the build process in order to verify the build quality of individual software components. But what about system level testing to ensure that all these components work together in a fully integrated system? In other words, how do you incorporate system testing as part of DevOps?
In this session we will share our experiences in doing just that. We will describe our environments where we use JMeter to continuously load and stress our system test applications. When new builds complete, we use Jenkins to kick off jobs that deploy updates to our test applications and test environments running on both on-prem and cloud platforms. Finally, we run processes to analyze log files for errors, and collect metrics so that we can better monitor the usage of our environments.
Rumana Haque is part of the System Verification Test group for WebSphere in IBM, where she has spent more than a decade. Her focus is on System Test Applications which are used to test WebSphere. This includes updating, maintaining and modernizing the applications, as well executing Stress tests on WebSphere using these applications using automation.
In her free time she enjoys gardening, and volunteering for the Girls Who Code organization.
I've been employed by IBM for 29 years. I started out as a C-programmer, and quickly moved into the QA/Test role as I enjoyed breaking software in it's early stages. I also had a knack for setting up environments that mimicked customer's environments that stressed out software that we were delivering. As software and systems became more complex, all of the manual steps to setup target environments became to tedious, so I sought out 'auto-magic' processes that could accelerate testing.