Planning Activities in Software Testing Process: A Literature Review and Suggestions for Future Research

Planning Activities in Software Testing Process: A Literature Review and Suggestions for Future Research

Software testing process consists of activities that implemented after it is planned and includingto document related testing activities. Test processes must be applied necessarily for able toclearly see the quality of software, the degree of reliability, whether it is ready for delivery, thedegree of effectiveness and remains of how much testing. One of the most important phase ofthese processes is test planning activities. Test planning activities directly affects the project'ssuccess in software projects. In this study, software testing process, and test planning activitiescarried out in this process was first clearly demonstrated by the literature review. Later, a basicsoftware testing process and test planning process were determined and explained step by step.In this way, it was aimed to give a different and deep perspective to the test planning activitiesand to raise awareness on the topic. As a result of the research, it was seen that the test planningactivities are not applied adequately at present, software testers, experts or researchers do nothave enough knowledge about the details of the method, and this situation causes very seriousnegative results in the delivery and cost in software projects. Finally, the topic was discussed indetail, and some conclusions and recommendations were given for the personnel in the field ofsoftware testing. In this point, the study is expected to contribute the literature.

___

  • Gürbüz, A., Kurt, A., Özbek, M., “Pitfalls in Software Testing Tool Selection”, III. National Software Engineering Symposium, Ankara, 1, (2007).
  • Britton, T., Jeng, L., Carver, G., Cheak, P., Katzenellenbogen, T., “Reversible Debugging Software”, University of Cambridge, Judge Business School, (2013).
  • Garousi, V., Felderer, M., Hacaloğlu, T., “Software test maturity assessment and test process improvement: A multivocal literature review”, Information and Software Technology, 85, 16-42, (2017).
  • Garousi, V., Coskuncay, A., Can, A. B., Demirors, O., “A survey of software engineering practices in Turkey”, J. Syst. Software, 108, 148–177, (2015).
  • Garousi, V., Zhi, J., “A survey of software testing practices in Canada”, J. Syst. Software, 86, 1354– 1376, (2013).
  • Grindal, M., Offutt, J., Mellin, J., “On the testing maturity of software producing organizations”, Testing: Academia & Industry Conference-Practice and Research Techniques, (2006).
  • Walia, M., Gupta, A., “Improvement in Key Project Performance Indicators through deployment of a Comprehensive Test Metrics Advisory Tool”, International Journal of Advanced Research in Computer Science, 8(5), (2017).
  • Wasif, A., "Metrics in software test planning and test design processes", (2007).
  • Pressman, R. S., "Software engineering: a practitioner's approach", Palgrave Macmillan, (2005).
  • Bormann, J., Fedeli, A., Frank, R., Winkelmann, K., “Combined Static and Dynamic Verification”, Research Report, FP6-IST-507219, Version 2-Public Version, (2005).
  • Korkmaz, O., Akman, I., “An MDP Based Simulation Model and An Example Application to Evaluate Software Quality”, VI. National Software Engineering Symposium (NSES), Ankara, 1, (2009).
  • Galin, D., “Software Quality Assurance – From theory to implementation”, Pearson – Addison Wesley, England, (2004).
  • Jamil, M. A., Arif, M., Abubakar, N. S. A., Ahmad, A., “Software Testing Techniques: A Literature Review”, In Information and Communication Technology for the Muslim World (ICT4M), 2016 6th International Conference on, pp. 177-182, IEEE, November, (2016).
  • De Nicola, G., di Tommaso, P., Rosaria, E., Francesco, F., Pietro, M., Antonio, O., “A grey-box approach to the functional testing of complex automatic train protection systems”, In European Dependable Computing Conference (pp. 305-317). Springer, Berlin, Heidelberg, (2005).
  • Garousi, V., Mäntylä, M. V., “When and what to automate in software testing? A multi-vocal literature review”, Information and Software Technology, 76, 92-117, (2016).
  • Khan, R., Srivastava, A. K., Pandey, D., “Agile approach for Software Testing process”, In System Modeling & Advancement in Research Trends (SMART), International Conference (pp. 3-6). IEEE, November, (2016).
  • Garousi, V., Pfahl, D., “When to automate software testing? A decision‐ support approach based on process simulation”, Journal of Software: Evolution and Process, 28(4), 272-285, (2016).
  • Dustin, E., Garrett, T., Gauf, B., “Implementing automated software testing: How to save time and lower costs while raising quality”, Addison-Wesley Professional, (2009).
  • Nidagundi, P., Novickis, L., “Introduction to lean canvas transformation models and metrics in software testing”, Applied Computer Systems, 19(1), 30-36, (2016).
  • Mustafa, K. M., Al-Qutaish, R. E., Muhairat, M. I., “Classification of Software Testing Tools Based on software Testing Methods”, In Second Int. Conf. on Computer and Electrical Engineering, ICCEE '09, , pp. 229–233. http://dx.doi.org/10.1109/ICCEE.2009.9, (2009).
  • O’regan, G., “A pratical approach to software quality”, Maple-Vail Book Manufacturing Group, Newyork, 73-77, (2002).
  • Kaveh, P., “A framework of the use of information in software testing”, The Faculty of the School of Engineering and Applied Science of the George Washington University in Partial Satisfaction of the Requirements for the Degree of Doctor of Science, May 16, (2010).
  • Black, R., “Managing the Testing Process”, Microsoft Press, December 1, (2004).
  • Calp, M. H., Arıcı, N., “An Expert Module Design and Implementation that Evaluation the C&K Metric Suite in Terms of Object Oriented Software Quality”, DEU Dokuz Eylül University Faculty of Engineering Journal of Science and Engineering, Vol: 14 No: 1 p. 55-68, (2012).
  • Akyuz, D., “Using Requirement Management Tool in Software Verification Process”, II. Software Quality and Software Development Tools Symposium, Ankara, 3-4 December, 1-2, (2010).
  • Amland, S., “Risk-based testing: Risk analysis fundamentals and metrics for software testing including a financial application case study”, Journal of Systems and Software, 53(3), 287-295, (2000).
  • Redmill, F., “Theory and Practice of Risk-based Testing”, Software Testing, Verification and Reliability, Vol. 15, No. 1, 3-20, (2005).
  • Agarwal, B. B., Tayal, S. P., Gupta, M., “Software engineering and testing”, Jones & Bartlett Learning, (2010).
  • Crespo, A. N., Jino, M., Argollo, M., Bueno, P. M. S., Barros, C. P., “Generic Process Model for Software Testing”, http://www.softwarepublico.gov.br/5cqualibr/xowiki/Teste-item13, (2010).
  • Mette, A., Hass, J., “Testing processes”, In Software Testing Verification and Validation Workshop, ICSTW'08, IEEE International Conference on, pp. 321-327, IEEE, (2008).
  • Kasoju, A., Petersen, K., Mäntylä, M. V., “Analyzing an automotive testing process with evidencebased software engineering”, Information and Software Technology, 55(7), 1237-1259, (2013).
  • Dybå, T., Dingsøyr, T., “Empirical studies of agile software development: a systematic review”, Information & Software Technology, 50 (9-10) 833–859, (2008).
  • Çatal, Ç., Diri, B., “New Approaches to Software Quality Classification Problem: Artificial Immune Systems”, III. National Software Engineering Symposium, Ankara, 1, (2007).
  • Tuna, O., “Software testing according to development process and architectural description”, M.Sc Thesis, Dokuz Eylül University Graduate School of Natural and Applied Sciences, İzmir, 1, (2005).
  • Lewis, E. W., “Software Testing and Continuous Quality Improvement, 3nd ed.”, A CRC Pres Company, USA, ISBN: 978-1-4200-8073-5, s.167-194, (2009).
  • Mosley, D. J., Posey B.A., “Just Enough Software Test Automation”, Prentice Hall PTR, USA, 10, (2002).
  • Muller, T., Graham, D., Friedenberg, D., Veendendal, E., “International Software Testing Qualifications Board (ISTQB)”, Foundation Level Syllabus, USA, 10, (2007).
  • Camargo, K. G., Ferrari, F. C., Fabbri, S. C., “Characterising the state of the practice in software testing through a TMMi-based process”, Journal of Software Engineering Research and Development, 3(1), 7, (2015).
  • Software & Systems Engineering Committee, “IEEE standard for software and system test documentation”, Fredericksburg, VA, USA: IEEE Computer Society, (2009).
  • Rao, D. N., Srinath, M. V., Bala, P. H., “Reliable code coverage technique in software testing”, In Pattern Recognition, Informatics and Mobile Engineering (PRIME), International Conference on, pp. 157-163, IEEE, (2013).
  • Gürbüz, A., “Software test engineering", Papatya Publishing Education, İstanbul, 34, (2010).
  • Software QATest.com, “What's a 'test plan'?”, http://www.softwareqatest.com/qatfaq2.html#FAQ2_6b, 2011. (Access Date: 01.02.2018).
  • Mustafa, K., Khan, R.A., “Software Testing: Concept and Practices”, India, Lucknow, Oxford: Alpha Science International, 194-211, (2007).
  • Tiftik, N., Öztarak, H., Ercek, G., Özgün, S., “Verification activities in system/software development process", III. National Software Engineering Symposium, Ankara, 1-2, 2007.
  • Afzal, W., Alone, S., Glocksien, K., Torkar, R., “Software testing process improvement approaches: A systematic literature review and an industrial case study”, Journal of Systems and Software, 111, 1-33, (2016).
  • Bentley, J. E., Bank, W., Charlotte, N. C., “Software Testing Fundamentals—Concepts, Roles, and Terminology”, SAS Institute Inc., SUGI 30 Proceeding, USA, 10-13 April, (2005).
  • Demir, D., “Software testing and quality assurance activities in industry”, I. National Software Engineering Symposium, İzmir, 23-25 October, (2003).
  • IEEE 610.12.1990: IEEE 610.12, Glossary of Software Engineering Terminology, New York, (1990).
  • Smith, M. D., Robson, D. J., “Object oriented programming the problems of validation”, Software Maintenance, (ICSM '90) Proceedings, IEEE International Conference, CH2921-5/90/0000/0272, (1990).
  • ANSI Std-1991, “Standard glossary of software engineering terminology (ANSI)”, The institute of electrical and electronics engineers inc., (1991).
  • CaBIG-NCI, “Test Plan”, https://cabig.nci.nih.gov/.../Test%20Plan%20Template_Baseline.doc, (2007).
  • Bayar, V., “Process Model for Component Oriented Software Development", II. National Software Engineering Symposium (NSES), Ankara, 2, (2005).
  • Linux Users Association of Turkey, “Pardus Software System and Bug Tracking System”, http://seminer.linux.org.tr/wpcontent/uploads/2010/06/semen_cirit_pardus_yazilim_testleri_ve_hata _takip_sistemi_03042010.pdf , (2010).
  • Coley Consulting, “Software Testing Exit Criteria”, http://www.coleyconsulting.co.uk/testing-exitcriteria.htm, (2010).
  • Glenford, M., “The Art of Software Testing”, Wiley, ISBN 978-0-471-46912-4, (2004).
  • Eickehnann, N. S., Richardson, D. J., “An Evaluation of Software Test Environment Architectures”, In Proceedings of ICSE'1996, pp.353-364, (1996).
  • Clarke, L. A., Richardson, D. J., Zeil, S. J., “TEAM: A support environment for testing, evaluation, and analysis”, In ACM SIGSOFT Software Engineering Notes, Vol. 13, No. 5, pp. 153-162, ACM, (1989).
  • Karaduman, Ö., Ademoğlu, C., Mert, E., “Automatic Test Approach in Real Time Systems", II. Software Quality and Software Development Tools Symposium, Ankara, 3-4 December, 1-2, (2010).
  • Alam, M. N., "Software test automation myths and facts", Benchmarkqa Publication Archive, (2007).
  • Aptest.com, “Bug and Defect Tracking Tools”, http://www.aptest.com/bugtrack.html, (2011).
  • Hoffman, M., Kuhn, N., Weber, M., Bittner, M., “Requirements for Requirements Management Tools”, Proceedings of the Requirements Engineering Conference 12th IEEE International Washington, DC, USA. IEEE Computer Society, (2004).
  • Akar, B., Dinçer, K., Tümay, A., “Automation of Software Product and Process Measurements ", II. National Software Engineering Symposium (NSES), Ankara, 2, (2005).
  • Wiegers, K., “A software metrics primer”, Software Development-San Francisco-, 7, 39-44, (1999).