Don't mock internal functions and methods, mock external dependencies. How to do that? This presentation will present a framework and practical example of creating Surrogate dependencies (think custom proxies, similar to WireMock). They are based on data collected from Integration tests to create environments where target applications can be executed offline and be subject to advanced security, quality and performance testing. All data is stored natively (JSON, XML) and Git is used for content versioning and simulation.
YOU MAY ALSO LIKE:
- Master Application Deployment and Scaling with Kubernetes and Docker (in London on 28th February - 1st March 2019)
- Uncle Bob Martin's Clean Code Workshop on Agile Software Craftsmanship (in London on 11th - 12th April 2019)
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 30th September - 2nd October 2019)
Dinis is focused on creating Application Security teams and providing Application Security assurance across the SDL (from development, to operations, to business processes, to board-level decisions). His focus is in the alignment of the business’s risk appetite with the reality created by Applications developed internally, outsourced or purchased. He is also an active Developer and Application Security Engineer focused on how to develop secure applications. A key drive is on 'Automating Application Security Knowledge and Workflows' which is the main concept behind the OWASP O2 Platform.