Agenda
Automated Testing Roundtables
Andrew Fray (Quality Engineering, Automated AF)
Track:
Programming, Production & Team Leadership
Audience Level:
All
Format:
Roundtable
Vault Recording: TBD
Audience Level: All
Day 1: Process
Automated testing provides a team with stability across development, allowing early feedback, fast iteration and empowering QA. Yet investing in automation has a bad reputation in the industry, where just-ship-it is the mantra. Maybe, as the market becomes increasingly competitive, its time has finally come.
On Day 1 we prefer to discuss the people that write the tests and the workflows used to reinforce them. How does the process work in your studio? Are the engineers responsible for automated tests, or QA? Are QA silo'd or integrated? What could be better? What doesn't work?
These roundtables bring together people of all experience levels and budgets to discuss how they currently, or would like to, use automated testing of any form. See atig.dev/gdc for more details and to join our discord!
Day 2: Legacy
Automated testing provides a team with stability across development, allowing early feedback, fast iteration and empowering QA. Yet investing in automation has a bad reputation in the industry, where just-ship-it is the mantra. Maybe, as the market becomes increasingly competitive, its time has finally come.
On Day 2 we prefer to talk about introducing automated testing to an organisation. Do you have a culture or a codebase that doesn't currently embrace automated testing? Are you having trouble getting people on-board, or maybe it was very easy and you can share why? Grand failures are just as interesting as successes!
These roundtables bring together people of all experience levels and budgets to discuss how they currently, or would like to, use automated testing of any form. See atig.dev/gdc for more details and to join our discord!
Day 3: Implementation
Automated testing provides a team with stability across development, allowing early feedback, fast iteration and empowering QA. Yet investing in automation has a bad reputation in the industry, where just-ship-it is the mantra. Maybe, as the market becomes increasingly competitive, its time has finally come.
On Day 3 we prefer to discuss the many faces of automation, from locally-run functional and unit tests, to server-driven continuous integration, and even external device farms. How do you do automated testing in your team? What works well for you? More interestingly, what didn't work and why?
These roundtables bring together people of all experience levels and budgets to discuss how they currently, or would like to, use automated testing of any form. See atig.dev/gdc for more details and to join our discord!
Automated testing provides a team with stability across development, allowing early feedback, fast iteration and empowering QA. Yet investing in automation has a bad reputation in the industry, where just-ship-it is the mantra. Maybe, as the market becomes increasingly competitive, its time has finally come.
On Day 1 we prefer to discuss the people that write the tests and the workflows used to reinforce them. How does the process work in your studio? Are the engineers responsible for automated tests, or QA? Are QA silo'd or integrated? What could be better? What doesn't work?
These roundtables bring together people of all experience levels and budgets to discuss how they currently, or would like to, use automated testing of any form. See atig.dev/gdc for more details and to join our discord!
Day 2: Legacy
Automated testing provides a team with stability across development, allowing early feedback, fast iteration and empowering QA. Yet investing in automation has a bad reputation in the industry, where just-ship-it is the mantra. Maybe, as the market becomes increasingly competitive, its time has finally come.
On Day 2 we prefer to talk about introducing automated testing to an organisation. Do you have a culture or a codebase that doesn't currently embrace automated testing? Are you having trouble getting people on-board, or maybe it was very easy and you can share why? Grand failures are just as interesting as successes!
These roundtables bring together people of all experience levels and budgets to discuss how they currently, or would like to, use automated testing of any form. See atig.dev/gdc for more details and to join our discord!
Day 3: Implementation
Automated testing provides a team with stability across development, allowing early feedback, fast iteration and empowering QA. Yet investing in automation has a bad reputation in the industry, where just-ship-it is the mantra. Maybe, as the market becomes increasingly competitive, its time has finally come.
On Day 3 we prefer to discuss the many faces of automation, from locally-run functional and unit tests, to server-driven continuous integration, and even external device farms. How do you do automated testing in your team? What works well for you? More interestingly, what didn't work and why?
These roundtables bring together people of all experience levels and budgets to discuss how they currently, or would like to, use automated testing of any form. See atig.dev/gdc for more details and to join our discord!
Takeaway
Attendees will discover common definitions around automated testing, how other studios are currently using it, what works well, and what doesn't. They will return to their studios and extol the benefits of automated testing, and that it doesn't have to be hard or time consuming to see returns on investment.
Intended Audience
Programmers and technical QA with experience or interest in automated testing. It's ok to be a novice - all ability levels encouraged.