Abstract:Agile Test is still a practice not well solved in the agile teams. The theory is beautiful, consistent and accepted but when you see in the practice, the hard work to implement leads the teams to leave that.
The difficulties are very close: frameworks not so easy, non-adherent culture, lack of technologic support, lack of technical knowledge, too much legacy code, too much time to run all tests, and so on.
This session will show a way to cross these difficulties, addressing every issue with real cases of agile and automation test, learned past 20 years of experience. And working on a legacy, critical, giant system and scaling teams.
What did work? What didn’t? Where did we have to invest? Is there any shortcut?
It is a history that will benefit technical developers, managers, and agile enthusiasts since it shows how attitudes make the difference when talking about overcoming obstacles and evolving.
Lessons Learned from Your Experience:During the presentation, we expect to answer, in a practical approach, questions such as:
- How many automation is really needed?
- How to structure the team?
- How to deal with integration tests and external systems?
- How much of each kind of test implement, considering unit, functional, integrated, and UI?
- What relation you have between investment and quality increasing?
- How to obtain better execution efficiency, considering technical aspects?
- What about when running on a single machine is not an option?
- Consider yet, having to scale more and more?
- How to deal with complex scenarios where the solution depends on the timeline?
- How to improve the performance of tests that depend on the data population?
- What happens if you decide to change the development language along the way?
- How to deal with intermittent test results?
- And testing concurrency?
- How to automate tests with production data, combining performance and production settings?
