Get in Touch

Course Outline

QA/CI

  • Understanding QA
  • Understanding CI
  • The costs associated with software development, refactoring, and error correction
  • Project identification and comprehension
  • Organizational benefits

DDD

  • Software development grounded in business requirements and DDD assumptions
  • Communication challenges between IT and Business
  • 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?
  • "White-box" and "black box" methods
  • The role of testing in agile methodologies
  • Whether TDD merely increases 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
  • XMI standard
  • Automatic documentation generation

CI Tools and Environment

  • CI tools and environment

Agile and CI/QA

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

Conclusion

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

Introduction to Testing

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

To Test or Not to Test

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

The Testing Process

  • Testing as a process and strategy
  • Identifying testing needs
  • Gathering requirements (use cases, user stories)
  • Scoping (choosing and prioritizing scenarios)
  • Designing tests
  • Preparing data
  • Preparing the environment
  • Creating or recording tests
  • Executing tests
  • Analysis and reporting
  • Conclusions and improvements
  • 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 requirements, and create tests
 28 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories