DevSecOps, with its principle that stresses that everyone is responsible for security, has become a practice that has been more popular than ever in the Work From Home (WFH) culture. In the development of DevSecOps-related projects, testing has been an integral part of the culture. Many teams working with the agile framework have already adopted the practice, with some still transitioning to getting accustomed to the practice in comparison to the traditional DevOps approach to testing.

This talk will discuss how testing with the Robot Framework within DevSecOps contrasts with the traditional DevOps approach within the agile environment, and show how to manage testing with the framework from start to finish. This will include how to plan for testing within DevSecOps, how writing test suites with the framework differs when we want to ensure that everyone is responsible to security, feedback mechanisms in standup meetings and how to maintain the culture within testing teams. This will also include implementing and managing the culture of iterative development, which requires continuous development of test suites as needed according to updates that are made, keeping security in applications as the top priority. Finally, I will talk about how these tests can then be automated in a DevSecOps context with a Cloud provider such as, in this case, Azure.

I will support my talk with a case study regarding the testing using Robot Framework done on one of my projects. Attendees will leave the talk feeling ready to implement the DevSecOps framework on their projects, and get the most out of security with the Robot Framework by doing so. As the WFH culture is going to stay for quite some time, it is going to be quite imperative to understand the DevSecOps culture to best prepare for it.