Agile Software Testing with Continuous Integration

Agile Software Testing is a series of testing practice that provides feesback to software quality issues in a timely and continuous manner following the principles of agile development.

Continuous Integration (CI) refers to all developers in a team merging their work several times a day.

QA/CI

• What is QA?
• What is CI
• The costs of software development, refactoring and fix errors
• Identifying and understanding the project
• Profit for the organization

DDD

• Software development based on business requirements, assumptions DDD
• Problems in communication IT-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

• Weight Method per Class
• Response For a Class
• Depth of Inheritance Tree
• Coupling Between Objects
• Lack of Cohesion of Methods
• Number of Children
• Cyclomatic complexity
• Metrics class
• Model Metrics
• Metrics for use

Software Testing

• What, when and how to test?
• The method of "white-box" and "black box"
• The role of testing in agile methodologies
• TDD only a potential increase in the cost of the project
• Unit testing
• Behavioral tests
• Functional tests

Refactoring

• What is refactoring?
• Debt technology
• Code smell
• Refactoring patterns

Documentation

• The role of documentation in agile methodologies
• What to document?
• Types of documentation
• Documentation and agile methodologies, or you can call (Working software over comprehensive documentation)?
• Standard XMI
• Automatic generation of documentation

Tools and Environment CI

• Tools and Environment CI

Agile and CI/QA

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

Summation

• Discussion
• Questions
• How do you begin the process of implementation?

Introduction to testing

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

Test or not to test

• Who is making decisions about what to test?
• The cost of testing irrelevant things
• Calculating ROI (what if something fails analysis)
• The role of Test Manager

The process of Testing

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

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 and write stories based on the requirements and create tests