Emerging Trends in Software Testing Introduction to course 12.9.2012 Lecture will start at 14.15 Material in Noppa: https://noppa.oulu.fi/noppa/ kurssi/811601s/luennot Ilkka Tervonen 1
SoSE is a doctoral programme on software and systems engineering (earlier a graduate school), started 2007. SoSE is funded by the Ministry of Education and now coordinated by University of Oulu. SoSE is organized into two subschools (SE & IS) and provides funding for 10 PhD students. SE-SoSE subschool (2/3 of funded positions) acts on software engineering focus area within seven universities (Helsinki University, Aalto University, Tampere University, Tampere University of Technology, Lappeenranta University of Technology, Åbo Akademi University, Oulu University) 2
Three major themes * Organizing and managing testing * Model-based testing * Exploratory testing Two other themes * division of labor in software testing * safety-critical testing 3
After completing the course, the student: Can analyse different ways to organize and manage software testing. Can evaluate the major techniques of agile testing and major approaches in model-based testing. Can analyse the possibilities and limitations of new testing approaches (e.g. exploratory testing) 4
A common factor for all speakers is the community * Testauksen osaamisyhteisö (TestausOSY) * FAST - Finnish Association for Software Testing. FAST organizes seminars and workshops in Helsinki, Tampere, Turku, Jyväskylä and Oulu FAST doesn t charge subscription You can join the FAST via announcement list * sytyke-testaus-kerho@pcuf.fi (in Finnish) * sytyke-fast@pcuf.fi (in English). 5
19.9.2012: Strategy and management in SW testing Jussi Kasurinen, Lappeenranta University of Technology 26.9.2012: SW testing in the cloud Leah Riungu-Kalliosaari, Lappeenranta University of Technology 3.10.2012: Software development and testing for intended quality Tero Pesonen, Lappeenranta University of Technology 6
10.10.2012: Model-based testing Dragos Truscan, Åbo Akademi University 17.10.2012: Test modeling Antti Jääskeläinen, Tampere University of Technology 24.10.2012: Domain-specific modeling for test Teemu Kanstrén, VTT, Oulu 7
31.10.2012: Exploratory testing approach Juha Itkonen, Aalto University 7.11.2012: Team exploratory testing sessions Soili Saukkoriipi, F-Secure, Oulu 14.11.2012: Testing for software professionals in Test is dead era TDD, ATDD and ET Maaret Pyhäjärvi, Granlund Oy 8
21.11.2012: Power of the crowds and on the division of labor in software testing Mika Mäntylä, Aalto University 28.11.2012: Testing of safety-critical software Matti Vuori, Tampere University of Technology 9
The assessment is based on report evaluation. The report should include analysis of eight lectures and related papers The length of the report should be about 20 pages and each student writes an individual report. brief summary of the lecture and answers to the questions given by the lecturer also more comprehensive consideration of some lecture topic The report should be returned to Ilkka Tervonen in two parts (SoSE students by e-mail (ilkka.tervonen@oulu.fi), Master students via Optima) * the deadline for the first part (including four lectures) is 31.10.2012 and for the second part (including four lectures) 15.12.2012. 10
Each lecturer will introduce 1-2 papers related her/ his lecture. As a background literature for the report the students can use for example Crispin L. and Gregory J., Agile testing: a practical guide for testers and agile teams, Addison-Wesley, 2009 Dustin E. and Garrett T. and Gauf B., Implementing Automated Software Testing, Addison-Wesley, 2009 Graham D. and Fewster M., Experiences of Test Automation: Case Studies of Software Test Automation, Addison-Wesley, 2012 Utting, M. and Legeard, B., Practical model-based testing: a tools approach, Elsevier, 2007 11
User needs Software in use Requirements specification Usability testing Acceptance testing Analysis - use case analysis - user interface design Architectural design Test plans Architectural testing System testing Software design Coding Unit testing Integration testing 12
External quality Internal quality Automated & Manual Supporting the Team Automated Mock-ups to validate GUI design Functional Tests Examples Story Tests Prototypes Simulations Unit Tests Component Tests Agile Testing Quadrants Business-Facing Q 2 Q 3 Q 1 Exploratory Testing Scenarios Usability Testing User Acceptance Testing Alpha/Beta Q 4 Emulating the way a real user would work the application Performance & Load Testing Security Testing ility Testing Manual Tools Testers use their creativity and intuition Critique Product Tests check nonfunctional requirements TDD by means of xunit tools Technology-Facing Crispin & Gregory 2009