Get in Touch

Course Outline

QA/CI

  • What is QA?
  • What is CI?
  • The costs of software development, refactoring, and error correction
  • Identifying and understanding the project
  • Benefits for the organization

DDD

  • Software development based on business requirements and DDD assumptions
  • Challenges in IT-Business communication
  • Domain Model

Best Practices

  • KISS principle and DRY
  • Coding standards
  • Creating reusable code through OOP and design patterns
  • Identifying and reducing cyclomatic complexity

Software Metrics

  • Weighted Methods per Class
  • Response for a Class
  • Depth of Inheritance Tree
  • Coupling Between Objects
  • Lack of Cohesion of Methods
  • Number of Children
  • Cyclomatic complexity
  • Class Metrics
  • Model Metrics
  • Use Metrics

Software Testing

  • What, when, and how to test?
  • The 'white-box' and 'black box' approaches
  • The role of testing in agile methodologies
  • TDD does not necessarily increase project costs
  • Unit testing
  • Behavioral tests
  • Functional tests

Refactoring

  • What is refactoring?
  • Technical debt
  • Code smells
  • Refactoring patterns

Documentation

  • The role of documentation in agile methodologies
  • What to document?
  • Types of documentation
  • Documentation in agile methodologies: Working software over comprehensive documentation
  • Standard XMI
  • Automatic generation of documentation

CI Tools and Environment

  • CI Tools and Environment

Agile and CI/QA

  • Planning and incremental development
  • Embracing Change
  • Short iterations
  • Interdisciplinary team
  • Extreme Programming, Code Review
  • Individuals and interactions over processes and tools

Conclusion

  • Discussion
  • Questions
  • How to begin the implementation process?

Introduction to Testing

  • Functional Tests
  • Regression Test
  • UAT Tests
  • Unit Tests
  • Usability Tests
  • Non-Functional Tests
  • Performance test
  • Load test
  • Stress test
  • Soak test

To Test or Not to Test

  • Who makes decisions about what to test?
  • The cost of testing irrelevant aspects
  • Calculating ROI (what if analysis fails)
  • The role of the Test Manager

The Testing Process

  • Testing as a process and a strategy
  • Identifying testing needs
  • Gathering requirements (use cases, user stories)
  • Scoping (choosing and prioritizing scenarios)
  • Designing tests
  • Preparing data
  • Preparing environment
  • Creating or Recording tests
  • Executing the test
  • Analysis and reports
  • Conclusions and improvement
  • When to stop testing

Product Owner and Tests

  • The customer representative and test priority
  • Prioritizing tests
  • Writing effective stories for UAT
  • Acceptance criteria
  • Group exercise to produce customer requirements, write stories based on the requirements, and create tests
 28 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories