This event is co-located with the conference ‘Digital Transformation: Methods and Tools’.
Digital strategies and their supporting infrastructures are being implemented with increasing rapidity; new frameworks and technologies such as Agile, DevOps , IoT, Robotics, SMACT (Social, Mobile, Analytics, Cloud and IoT) are proliferating, and consequently, the requirements for testing and quality assurance are changing. Now the UK Government is launching a new Digital Strategy, aiming to build on the UK’s success in digital innovation and consolidate its position as a global tech hub. As ever, testing is vital to ensure new technologies, infrastructures and applications work as they should.
The need for improvement, training and keeping abreast of the latest trends are as continuous as the testing process, and this conference gives testing professionals the opportunity to hear, share and learn from their peers as well as from experts who are passionate about testing.
Who should attend:
CDOs; CIOs; Software Testers and test managers; Test consultants; IT directors; Test practitioners and engineers; QA directors and managers; Development managers and developers; Delivery managers; CTOs.
Over the next few weeks we will announce further details of the agenda for 2017.
We are looking for speakers willing to share their experiences and stories about the constantly evolving software testing area. If you wish to submit a proposal to present at this event please fill in the speaker response form.
Here is a list of topics we would like to cover at this event:
Automatic Penetration Tests
5 July, London
Penetration testing is a healthy combination of manual and automated methods, and a necessary part of a secure SDLC. However, its manual nature means that it can slow down a delivery pipeline, perhaps to the point where it’s moved all the way to the right (post release).
Penetration Testing is a vital activity, discovering logic flaws that could lead to security vulnerabilities. It requires a degree of experience and intuition that cannot be fully replaced by automated tests, but automation is a method by which we can reduce the requirement for manual testing, and introduce regression tests for the issues it uncovers.
The application login flaws discovered through manual testing can often be explained by a failure to meet security requirements, or security requirements that are not sufficiently granular. If security requirements can be translated to specific acceptance criteria, and then tests driven by these acceptance criteria, perhaps we can reduce the potential for application logic flaws.
In this workshop, we will learn how some penetration testing can be automated and moved back to the left of a software delivery pipeline. We will:
To participate, you will need a laptop with the following installed: