Course details

Automated Testing and Dynamic Analysis

ATA Acad. year 2019/2020 Summer semester 5 credits

Current academic year

Coverage criteria. Control flow graph. Unit testing. Test doubles. Requirement-based testing. Bug localisation. Data-driven testing. Automatic generation of test data. Fuzz testing. Performance testing. Run-time monitoring. Testing of parallel programs. Test management. Reliability of test reports.

Guarantor

Smrčka Aleš, Ing., Ph.D. (DITS)

Course coordinator

Rogalewicz Adam, doc. Mgr., Ph.D. (DITS)

Language of instruction

Czech

Completion

Examination (written+oral)

Time span

  • 26 hrs lectures
  • 26 hrs projects

Assessment points

  • 70 pts final exam (written part)
  • 30 pts projects

Department

Department of Intelligent Systems (UITS)

Lecturer

Rogalewicz Adam, doc. Mgr., Ph.D. (DITS)
Smrčka Aleš, Ing., Ph.D. (DITS)

Learning objectives

To provide an overview of different approaches to software testing. The focus is put on automated software verification. To gain practical skill of tracing the program run and subsystem communication. To gain practical skill of software testing required by a quality assurance analyst.

Why is the course taught

Software testing is forefront in quality assurance. Since software designs rapidly increase in their complexity, there is a strong need for automation of each development phase, including quality assurance. Students will learn different approaches to automation of software testing and dynamic analysis based on tracing of program runs. Students are needed members of every development teams for their knowledge gained in this course.

Study literature

  • Spillner, A., Linz, T. , Schaefer, H.: Software Testing Foundations : A Study Guide for the Certified Tester Exam. Rocky Nook Computing. 2014. 296 s.. ISBN 9781937538422
  • Kaner, C., James, B., Pettichord, B.: Lessons Learned in Software Testing: A Context-Driven Approach. Wiley Computer Publishing, 2002, 286 s., ISBN 0-471-08112-4.
  • Marick, B.: The Craft Of Software Testing, Subsystem Testing, Prentice Hall PTR, 1995, ISBN 0-13-177411-5.
  • Ammann, P., Offutt, J.: Introduction to Software Testing. Cambridge University Press, 2008, 322 s. ISBN 978-0-511-39330-3.

Fundamental literature

  • Myers, G. J., Sandler, C., Badgett, T.: The Art of Software Testing, 3. vydání. John Wiley & Sons, 2011, 256 s., ISBN 978-1118031964
  • Farrell-Vinay, P.: Manage Software Testing. Auerbach Publications, 2008, 537 s., ISBN 978-0-8493-9383-9

Syllabus of lectures

  1. Model-based testing I 
    • Control flow graph, Interprocedural CFG.
    • Coverage-driven generation of test cases.
  2. Model-based testing II
    • Automation of unit tests.
    • xUnit test patterns (Mocking).
  3. Test fixture and test doubles.
  4. Requirement based testing.
    • Requirement classification.
    • Traceability.
    • Automation in Behaviour-driven development (BDD).
  5. Bug localization.
  6. Data-driven testing I 
    • Combinatorial testing.
    • Test data minimization.
    • API testing.
    • Systematic generation of test data.
    • Mutation testing.
  7. Data-driven testing II
    • Fuzz testing.
  8. Performance testing
    • Performance parameters.
    • Types and processes of performance testing.
  9. Run-time verification I 
    • Low-level tracing.
  10. Run-time verification II
    • Test properties, temporal properties, parametric properties.
    • Program instrumentation.
  11. Testing of parallel programs I 
    • Concurrency bug classification.
    • Contracts for concurrency.
    • Systematic vs. random testing.
    • Noise injection methods.
  12. Testing of parallel programs II
    • Atomrace and Eraser algorithms.
    • Vector clocks.
    • Fasttrack algorithm.
  13. Test management
    • Test prioritisation.
    • Test suite evaluation. Test flakiness.
    • Test reports. Reliability of reports. Accuracy, Precision, Recall, F1.

Syllabus - others, projects and individual work of students

  1. Design of automated test suite with knowledge of source code and/or requirements.
  2. Implementation of run-time monitor.

Progress assessment

Two projects, 15 points each.

Course inclusion in study plans

Back to top