A SkillsCast for this session is not available.
Acceptance Testing is one of the essential components of a healthy agile software development process; unfortunately this typically results in the creation of slow, brittle and highly complex UI based tests. These can leave development teams and businesses left wondering, is it worth it? By revisiting fundamentals this talk explores the role it should play in driving collaboration between business and software and how it can be best applied.
In this talk we discover an alternative approach to UI based testing that results in tests that are blazing fast, rock-solid and actually improve the architecture of your app's software. Increase you and your teams productivity and discover the secret to answering the question "Can we ship?" in seconds instead not days
YOU MAY ALSO LIKE:
- Track Lead: Brainstorms are Dead! - How 'Design Sprints' are Revolutionising 'Design Thinking' and Helping Companies Solve Big Problems and Test New Ideas Quickly (SkillsCast recorded in November 2018)
- Crafting Code with Sandro Mancuso (Online Course on 13th - 14th May 2021)
- Android Architecture with Jorge Ortiz-Fuentes (Online Course on 17th - 19th May 2021)
- P3X — People Product Process eXchange 2021 (Online Conference on 15th - 16th September 2021)
- Accessibility in Flutter (SkillsCast recorded in August 2020)
- Keynote: SWARMing into Action (SkillsCast recorded in October 2019)
In The Brain of Paul Stringer
Paul is an iOS expert combining skills in mobile product design with extensive software engineering experience. An influencer and leader having worked with development teams, key stakeholders and corporate clients incl. Apple and Sky.
After years masquerading as a professional developer, Paul discovered 'Clean Code' and began a journey to a new understanding of what being a software professional meant. That journey continues through working with best practices such as TDD, Acceptance Testing and Pair Programming "as standard" in the pursuit of building the best possible software; Paul believes in the principle of getting software right early, and then keeping it working as intended.