Syllabus for Software Testing

Mjukvarutestning

Syllabus

  • 5 credits
  • Course code: 1DL610
  • Education cycle: Second cycle
  • Main field(s) of study and in-depth level: Computer Science A1N, Technology A1N

    Explanation of codes

    The code indicates the education cycle and in-depth level of the course in relation to other courses within the same main field of study according to the requirements for general degrees:

    First cycle

    • G1N: has only upper-secondary level entry requirements
    • G1F: has less than 60 credits in first-cycle course/s as entry requirements
    • G1E: contains specially designed degree project for Higher Education Diploma
    • G2F: has at least 60 credits in first-cycle course/s as entry requirements
    • G2E: has at least 60 credits in first-cycle course/s as entry requirements, contains degree project for Bachelor of Arts/Bachelor of Science
    • GXX: in-depth level of the course cannot be classified

    Second cycle

    • A1N: has only first-cycle course/s as entry requirements
    • A1F: has second-cycle course/s as entry requirements
    • A1E: contains degree project for Master of Arts/Master of Science (60 credits)
    • A2E: contains degree project for Master of Arts/Master of Science (120 credits)
    • AXX: in-depth level of the course cannot be classified

  • Grading system: Fail (U), Pass (3), Pass with credit (4), Pass with distinction (5)
  • Established: 2017-03-09
  • Established by:
  • Revised: 2022-10-18
  • Revised by: The Faculty Board of Science and Technology
  • Applies from: Autumn 2023
  • Entry requirements:

    120 credits including 15 credits in mathematics and 60 credits in computer science/engineering, including a second course in programming in an imperative language and object-oriented programming. Participation in Algorithms and Data Structures I. Proficiency in English equivalent to the Swedish upper secondary course English 6.

  • Responsible department: Department of Information Technology

Learning outcomes

On completion of the course, the student should be able to:

  • describe key techniques and standards in software testing,
  • explain and evaluate strategies for software testing for both complete program life cycles and individual phases,
  • specify and design test cases and test programs,
  • produce appropriate documentation for test management, including test plans, test schedules and test progress monitoring,
  • develop code using test driven development,
  • be able to use suitable testing tools and discuss their range and capabilities.

Content

Testing methodologies and their practical application in software development. Different aspects of testing: Black box testing where testing is done without knowledge of how the program is written; white box testing where the developer tries to guarantee that every statement, execution path and method is executed during the testing and finally unit testing which is a practical design methodology where test cases are developed as each function or method is written.

Instruction

Lectures, laboratory exercises.

Assessment

Written exam. Oral and written assessment of exercises.

If there are special reasons for doing so, an examiner may make an exception from the method of assessment indicated and allow a student to be assessed by another method. An example of special reasons might be a certificate regarding special pedagogical support from the disability coordinator of the university.

Other directives

This course cannot be included in a degree together with Software testing and maintenance DV2 (1DL600), Testing Methodology (1DT053).

Syllabus Revisions

Reading list

Reading list

Applies from: Autumn 2023

Some titles may be available electronically through the University library.

Course literature

  • Ammann, Paul; Offutt, Jeff Introduction to software testing

    Cambridge: Cambridge University Press, 2008

    Find in the library

Print syllabus and reading list
Print