Tests your pipeline might be missing
Developing a delivery pipeline means more than just adding automated deploys to the development cycle. To be successful, tests of all types must be incorporated throughout the process in order to be sure that problems aren’t slipping through. Most pipelines include unit tests, functional tests, and acceptance tests, but those aren’t always enough. I’ll present some types of testing you might not have considered, or at least might not have considered the importance of. Some types will address code quality, others code security, and some the health and security of the pipeline itself. This talk is aimed at people that are trying to build confidence in their continuous delivery pipeline. I’ll talk about specific tools we used to supplement our pipeline testing. I won’t get into how to use each tool-- this is more of a series of teasers to encourage people to look into the tools, and even letting them know what types of tools and testing opportunities are out there.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Tests your pipeline might be missing
Semelhante a Tests your pipeline might be missing (20)
Mais de Gene Gotimer
Mais de Gene Gotimer (19)
Último
Último (20)
Tests your pipeline might be missing
- 1. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 1 @CoverosGene Tests Your Pipeline Might Be Missing
- 2. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 2 @CoverosGene Everything can’t be first or last Do just enough of each type of testing early in the pipeline to determine if further testing is justified.
- 3. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 3 @CoverosGene Check your code footprint mvn dependency:tree mvn dependency:analyze mvn com.ning.maven.plugins: maven-dependency-versions-check-plugin
- 4. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 4 @CoverosGene Poor quality code is harder to maintain … and harder to secure
- 5. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 5 @CoverosGene Are your libraries up-to-date?
- 6. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 6 @CoverosGene Test your unit tests
- 7. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 7 @CoverosGene Test what users can’t do … or at least shouldn’t User role testing
- 8. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 8 @CoverosGene Security test by piggy-backing on functional tests OWASP ZAP passive proxy active scanner fuzzer
- 9. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 9 @CoverosGene Repeatable, reliable deployments … and test that through practice
- 10. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 10 @CoverosGene Audit yourself
- 11. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 11 @CoverosGene Is the base system secure?
- 12. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 12 @CoverosGene Are your packages up-to-date?
- 13. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 13 @CoverosGene How’s performance?
- 14. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 14 @CoverosGene Test the database
- 15. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 15 @CoverosGene What are your users doing?
- 16. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 16 @CoverosGene Practice failure
- 17. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 17 @CoverosGene Scan all the systems Don’t forget the infrastructure
- 18. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 18 @CoverosGene Protect against hackers … even on dev and test systems
- 19. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 19 @CoverosGene Don’t expect that your pipeline is done A little better is still better. Keep improving.
- 20. © COPYRIGHT 2016 COVEROS, INC. ALL RIGHTS RESERVED. 20 @CoverosGene Test your pipeline … if it goes down, everything goes down