SWE 2721 - Introduction to Software Verification

2 lecture hours 2 lab hours 3 credits

• Explain why testing is important to software development 
• Explain the relationship between verification and validation 
• Compose accurate and detailed defect reports and record defects into a defect tracking system 
• Using appropriate coverage criteria and testing theory, design and construct high quality testing approaches and prepare tests in a logical, organized fashion 
• Apply testing theory to design tests based on presented test criteria 
• Analyze the effectiveness of testing using testing metrics, mutation testing, and other techniques 
• Design and implement test cases using mock objects 
• Analyze a given piece of source code for complexity and testability
• Use Capture-Replay tools to automate GUI based testing

• Experience working with the Java programming language.

Discrete math

• Graph theory/directed graphs
• Set theory
• Predicates/Boolean algebra

Software engineering tools and practices

• JUnit test case development
• Version control (i.e. GIT) tool usage (Commit, clone, branch, merge, diff, etc.)
• Working with IDEs (importing projects, stepping, breakpoints, etc.)

• Case studies in software failure
• Software testing foundations
• Test automation and testing tools
• Criteria based test design
• Input space partitioning
• Equivalence classes
• Boundary value analysis
• Graph theory
• Graph theory and source code
• Logic coverage
• Cyclomatic complexity and loop testing
• Testing from use cases
• Mock objects and test doubles
• Finite state machine testing
• Syntax based testing and regular expressions
• Mutation testing
• Putting tests first
• Test plans
• GUI testing
• Exploratory testing

• Developing rudimentary tests
• Developing automated unit tests
• Input domain-based testing
• Boundary value and equivalence class testing
• Code coverage and path-based testing
• Logic coverage testing
• Testing using mock objects
• Finite state machine testing
• GUI testing with selenium
• Mutation testing
• Testing from use cases and activity diagrams
• Exploratory testing of an application