On the Characterization of the SDET Role in Agile Projects: Expected Skills, Responsibilities, and Practices
Resumo
Software Development Engineer in Test (SDET) is a formal title for a software tester in software development context. In this paper, we report on a systematic literature review on the SDET role in agile projects. From the 27 se- lected papers, we extracted SDET role’ skills, practices and responsibilities. For instance, we found that motivation, flexibility, and work experience in software engineering are important skills for the SDET be able to perform her work. We also found that developing the system, performing automated unit test, and per- forming exploratory tests are among the main responsibilities of a SDET. Test automation, A/B test, and Behavior-Driven Design are some of the most cited practices of this role in agile projects.
Referências
Abrahamsson, P., Marchesi, M., and Maurer, F. (2009). Agile Processes in Software Engineering and Extreme Programming. Springer, Pula, Italy.
Agarwal, N. and Deep, P. (2014). Obtaining better software product by using test first programming technique. In Proceedings of International Conference-Confluence The Next Generation Information Technology Summit, pages 742–747, Noida, India. IEEE.
Almog, D. and Tsubery, Y. (2015). How the repository driven test automation (rdta) will make test automation more efficient, easier & maintainable. In Proceedings of India Software Engineering Conference, pages 196–197, Bangalore, India. ACM.
Anand, T. and Mani, V. (2015). Practices to make agile test teams effective: challenges and solutions. In Proceedings of International Conference on Global Software Engineering Workshops, pages 7–11, Ciudad Real, Spain. IEEE.
George, B. and Williams, L. (2004). A structured experiment of test-driven development. Information and software Technology, 46(5):337–342. Anais da 1o Escola Regional Engenharia de Software (ERES 2017) em Alegrete, RS, Brasil, 20 de outubro de 2017
Hammond, S. and Umphress, D. (2012). Test driven development: the state of the prac-tice. In Proceedings of the Annual Southeast Regional Conference, pages 158–163, Tuscaloosa, USA. ACM.
Haugset, B. and Hanssen, G. K. (2008). Automated acceptance testing: A literature review and an industrial case study. In Agile Conference, pages 27–38, Toronto, Canada. IEEE.
Kim, E. and Ryoo, S. (2012). Agile adoption story from Nhn. In Proceedings of the Annual Computer Software and Applications Conference, pages 476–481, Izmir, Turkey. IEEE.
Little, T., Elliott, S., Hughes, J., and Simion, F. (2012). Leveraging global talent for effective test agility. In Agile Conference, pages 165–171, Dallas, USA. IEEE.
Page, A. and Johnston, K. (2008). How We Test Software at Microsoft. Microsoft Press.
Park, S. S. and Maurer, F. (2008). The benefits and challenges of executable acceptance testing. In Proceedings of the International Workshop on Scrutinizing Agile Practices or shoot-out at the Agile corral, pages 19–22, Leipzig, Germany. ACM.
Prechelt, L., Schmeisky, H., and Zieris, F. (2016). Quality experience: a grounded theory of successful agile projects without dedicated testers. In Proceedings of International Conference on Software Engineering, pages 1017–1027, Austin, USA. ACM.
Rahman, A. A. U., Helms, E., Williams, L., and Parnin, C. (2015). Synthesizing continuous deployment practices used in software development. In Agile Conference, pages 1–10, Washington, USA. IEEE.
Smith, M., Miller, J., and Daeninck, S. (2009). A test-oriented embedded system production methodology. Journal of Signal Processing Systems, 56(1):69–89.
Solis, C. and Wang, X. (2011). A study of the characteristics of behaviour driven development. In Proceedings of Conference on Software Engineering and Advanced Applications, pages 383–387, Oulu, Finland. Austrian Computer Society.
Start (2017). Start — lapes - laboratório de pesquisa em engenharia de software. "http://lapes.dc.ufscar.br/tools/start_tool" -Accessed in September 2017.
Sultanía, A. K. (2015). Developing software product and test automation software using agile methodology. In Proceedings of the International Conference on Computer, Communication, Control and Information Technology, pages 1–4, Hooghly, India. IEEE.
Tripp, J. F., Riemenschneider, C., and Thatcher, J. B. (2016). Job satisfaction in agile development teams: Agile development as work redesign. Journal of the Association for Information Systems, 17(4):267.
Williams, L., Brown, G., Meltzer, A., and Nagappan, N. (2011). Scrum + engineering practices: Experiences of three microsoft teams. In Proceedings of the International Symposium on Empirical Software Engineering and Measurement, pages 463–471, Washington, USA. IEEE.