Part 1: Agile Overview:
Team-Driven Development is a vital component of the Agile Software Development Methodology and the overall DevOps movement. So, it is helpful to have, at a minimum, a high-level understanding of Agile practices and scrum ceremonies, and TDD fits into the overall Agile, Scrum, and DevOps landscape. In addition, part 1 serves as a levelling exercise to ensure that team members speak the same language during upcoming labs and discussions.
1. Components of Agile
- User Stories.
- Tasks.
- Bugs.
- Automated Builds.
- Automated Tests.
- Continuous Inspection.
2. The Role of TDD in Agile Development
- Automated Unit Tests.
- Automated Acceptance Tests.
2. The Role of TDD in Agile Development
- Automated Unit Tests.
- Automated Acceptance Tests.
Part 2: Unit Testing:
Unit Testing is a critical component of Team-Driven Development (TDD). Small code units are tested throughout the development process, which isolates functionality to ensure that individual parts work correctly.
1. Unit Test Fundamentals
- Reason to do Unit Testing.
- What to Test: Right BICEP.
- CORRECT Boundary Conditions.
- Properties of Good Tests.
2. Frameworks
- What is JUnit.
- JUnit Building Blocks.
- Test Cases.
- Test Suites.
- Examples.
3. Agile Testing Strategy
- Agile Testing Quadrant.
- Automation Pyramid.
- Assertions.
4. Test Attributes
- Setup / TearDown.
- JUnit Lifecycle.
- System Under Test.
- Test Design Strategy.
- Naming our Tests.
- Exceptions.
5. Lab: Introduction to Unit Testing
- IDE and Project Setup.
- Running our first Unit Test.
- Explore Junit framework.
- Test Attributes.
- Assert Statements.
Part 3: Team-Driven Development:
Essential TDD techniques require developers to write programs in short development cycles, and critical steps must be taken. Tests are created before the code is written. Once the code passes testing, it is refactored to adhere to the most effective and acceptable standards.
1. TDD Rhythm
- TDD Overview.
- Red, Green, Refactor.
- TDD Benefits.
2. Sustainable TDD
- Development without TD.
- Test Last.
- Test Last in Parallel.
- Test-Driven Development.
3. Supporting Practices
- Collective Ownership.
- Continuous Integration.
4. Eight Wastes of Software Development
- Ripple effect of defects.
- Partially Done Work.
- Extra Features.
- Relearning.
- Handoffs.
- Task Switching.
- Delays.
- Defects.
5. Test Automation
- Automate, Automate, Automate.
- Automate Early and Often.
- Additional Topics Identified.
6. Lab: Team-Driven Development
- Start Team-Driven Development on our example App.
- Write unit team cases.
- Experience RED, Green, Refactor Process.
Part 4: Principles of Agile Development
TDD is directly influenced by design, so it will be a priority to consider this during implementation. Considering design principles will enable teams to experiment with different approaches and gear towards more functional programming.
1. Design Principles Overview
- Coding Principles.
- isolation of the SUT.
- Developing independently testable units.
2. Test doubles
- Introducing test doubles.
- Stubs.
- Fakes.
- Mocks.
3. Lab: Continue development on example App
- Setting up Test doubles for our example app.
- Discuss and implement Mocking.
Part 5: Refactoring
Refactoring is another essential technique of TDD, and most software development teams are most likely doing some form of refactoring regularly. Refactoring can be used in several different workflows, which will be explored in this Part.
1. Why Refactor?
- Red, Green, Refactor.
- Benefits.
- Development without TDD.
2. Refactoring Methods
3. Refactoring Cycle
- Reduce Local Variable Scope.
- Replace Temp with Query.
- Remove Dead Code.
- Extract Method.
- Remove Unnecessary Code.
4. Lab: Continue our example project
- Implement new test cases.
- TDD Cycle.
- Discuss and implement Refactoring Needs.
Part 6: Pair Programming:
Pair Programming is an effective way to improve code quality. In this Part, we will discuss pairing and how it leads to better software design and a lower development cost.
1. Pair Programming & Advantages of Pairing
- Both Halves of the Brain.
- Focus.
- Reduce Interruptions.
- Reduce Resource Constraints.
- Multiple Monitors.
- Challenges.
2. Pairing Techniques
- Pair Rotation.
- Ping Pong Pairing..
- Promiscuous Pairs
- Pair Stairs.
- Cross-Functional Pairing.
Lab – Experience pair programming and continue developing our example app.
Part 7: Acceptance Team-Driven Development (ATDD) & Behaviour-Driven Development (BDD)
Acceptance Tests are a basic form of functional specification, and Behaviour Driven Development dictates what happens as an effect of these tests being run. In this Part, we will cover the difference between them and how they are closely related.
1. Acceptance Testing
- Acceptance Tests.
- Why Acceptance Tests?.
- Acceptance Test Execution.
- Who Writes Acceptance Tests.
- Pair Test Writing.
2. Best Practices for Effective Testing
- Keys to Good Acceptance Tests.
- Writing Acceptance Criteria.
- Acceptance Test Example.
- Acceptance Test-Driven Development (ATDD).
3. BDD vs. ATDD
- Specification by Example.
- BDD Frameworks.
- BDD Examples.
4. Lab: Experience ATDD and BDD
- Experience ATDD or BDD and discuss the impact on TDD.
Part 8: Simulation:
- Experience Agile development with team-driven development, behaviour-driven development and pair programming.