Practical Course on Software Testing (WS2017)

Teaching Staff: Patrick Harms, Fabian Trautsch
Type: 
Practical Course

Organisation

  • Timeframe:
    • 3-week block course
    • Tentatively end of March to beginning of April 2018
  • Modules:
    • M.Inf.1804: Praktikum Software-Qualitätssicherung (unbenotet) / Practical Course in Software Quality Assurance (not graded)
  • Workload:
    • 6 ECTS / 4SWH 
  • Language:
    • English
  • Registration:
    • Registration for the course in Stud.IP is required in order to be able to access course materials and facilitate efficient course organization and coordination.
    • At most 15 students can join the course.
    • The minimum number of participants for the course is 4.
  • Further requirements
    • Physical attendance during the course is mandatory.
    • Programming skills in Java will be required.
    • It may be required to bring your own device.
  • Participant selection
    • The attendance in the first session is mandatory
    • If you do not attend in the first session, you can not participate in the course
    • If there are more than 15 people in the first session, we chose the participants for the course at random out of all present students

Goals (from the module description)

Participants in the course should expect the following learning outcomes upon successful completion of the course:

  • Learn to become acquainted with up-to-date methods and software tools for software quality assurance
  • Learn to select methods and tools for given practical problems in software quality assurance
  • Learn to apply methods and tools for given practical problems in software quality assurance
  • Learn to assess methods and tools for given practical problems in software quality assurance by performing experiments

Content

The Practical Course on Software Testing covers the following topics:

  • Testing in different ways, assessing advantages and disadvantages of different approaches (manual, automated, model-based, etc.)
  • Testing for different reasons (functionality, regression, conformance, interoperability, load, performance, etc.)
  • Testing in at different levels (unit, component, integration, system, acceptance)
  • Test automation and evaluation
  • Continuous integration

For further information

Main menu 2

2011 © Software Engineering For Distributed Systems Group