Acceptance Testing of Web Applications with Test Description Language

Łukasz Olek, Bartosz Alchimowicz, Jerzy Nawrocki

Abstract


Acceptance tests are usually created by a client after a part of a system is implemented. However, some methodologies propose the elaboration of test cases before implementing a system. This approach increases the probability of system implementation that fulfills requirements, but may be problematic for customers and testers. To allow acceptance testing in such conditions, we propose to define test cases by recording them on an interactive mockup (a low detailed user-interface prototype). The paper focuses on Test Description Language, a notation used to store test cases.

Keywords


acceptance test case, use case, mockup, Test Description Language

Full Text:

PDF

References


Framework for Integrated Test (FIT). URL http://fit.c2.com/.

Bartoli A., Davanzo G., De Lorenzo A., Medvet E., Sorio E.: Automatic Synthesis of Regular Expressions from Examples. Computer, 2013.

Beck K., Fowler M.: Planning Extreme Programming. Addison-Wesley, 2000.

Burns D.: Selenium 2 Testing Tools: Beginner’s Guide. Packt Publishing Ltd, 2012.

Close D., Robbins A., Rubin P., Stallman R., van Oostrum P.: The AWK Manual, 1995.

Constantine L. L., Lockwood L. A. D.: Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design. ACM Press/Addison-Wesley Publishing Co., New York, NY, USA, 1999. ISBN 0-201-92478-1.

Haugset B., Hanssen G.K.: The Home Ground of Automated Acceptance Testing: Mature Use of FitNesse. Agile Conference (AGILE), 2011, pp. 97–106. IEEE, 2011.

ISO: ISO/IEC/IEEE 24765:2010 – Systems and software engineering – Vocabulary. International Organization for Standardization, Geneva, Switzerland, 2010.

Leotta M., Clerissi D., Ricca F., Tonella P.: Capture-replay vs. programmable web testing: An empirical assessment during test case evolution. In: Reverse Engineering (WCRE), 2013 20th Working Conference on, pp. 272–281, IEEE, 2013.

Martin R., Melnik G., Inc O.: Tests and Requirements, Requirements and Tests: A Möbius Strip. Software, IEEE, vol. 25(1), pp. 54–59, 2008.

Melnik G.: Empirical Analyses of Executable Acceptance Test Driven Development. Ph.D. thesis, University of Calgary, 2007.

Nawrocki J.R., Olek L.: Use-Cases Engineering with UC Workbench. In: K. Zielinski, T. Szmuc (eds.), Software Engineering: Evolution and Emerging Technologies, Frontiers in Artificial Intelligence and Applications, vol. 130, pp. 319–329. IOS Press, 2005. ISBN 978-1-58603-559-4.

Olek L., Nawrocki J.R., Ochodek M.: Enhancing Use Cases with Screen Designs. In: Z. Huzar, R. Kocí, B. Meyer, B. Walter, J. Zendulka, eds., CEE-SET, Lecture Notes in Computer Science, vol. 4980, pp. 48–61. Springer, 2008. ISBN 978-3-642-22385-3.

Pressman R.: Software Engineering – A practitioners Approach. McGraw-Hill, 2004.

Rettig M.: Prototyping for tiny fingers. Communication of the ACM, vol. 37(4), pp. 21–27, 1994. ISSN 0001-0782.

Roehm T., Tiarks R., Koschke R., Maalej W.: How Do Professional Developers Comprehend Software? In: Proceedings of the 34th International Conference on Software Engineering, ICSE ’12, pp. 255–265. IEEE Press, Piscataway, NJ, USA, 2012. ISBN 978-1-4673-1067-3.

Shore J.: FIT and User Interface. URL http://www.jamesshore.com/Blog/Fit-and-User-Interfaces.html.

Snyder C.: Paper Prototyping: The Fast and Easy Way to Define and Refine User Interfaces. Morgan Kaufmann Publishers, 2003.

Sommerville Y., Sawyer P.: Requirements Engineering. A Good Practice Guide. Wiley and Sons, 1997.

Wynne M., Hellesoy A.: The cucumber book: behaviour-driven development for testers and developers. Pragmatic Bookshelf, 2012.




DOI: https://doi.org/10.7494/csci.2014.15.4.459

Refbacks

  • There are currently no refbacks.