Course: Unit Testing with Java · 2 days [D4]

Course: Unit Testing with Java · 2 days [D4]

from 78.00

Learn how to create unit tests in Java.

Duration: 2 days / 4 evenings / 14 hours
Audience: Developers, Development Leads & Managers, Test Developers, Scrum Masters
Certification: Upon training completion
Courseware licensing: 3 months or perpetual

Learning cases and programming katas:
 Fit unit testing in an Agile life cycle
 Set unit test boundaries and coverage
 Deal with dependencies
 Write unit tests with AAA pattern
✓ Use unit testing frameworks (JUnit and others)
 Use mock objects and isolation frameworks
✓ Organise and execute unit tests

- View price at top after selecting Format / Public event
- For zone-dependent pricing, please select your zone
- For discounts and terms, please view pricing details

Format / Public event:
Add to cart & Register

1. Agile Testing Transformation

  • Testing as part of "Definition of Done"
  • Shift-left testing & early test automation
  • Agile testing, shared ownership and collaboration
  • Test-driven development (TDD)

2. Unit testing concepts

  • Selecting the right unit boundaries
  • Creating a basic unit test
  • Characteristics of good unit tests
  • Unit testing frameworks
  • Dependencies and test doubles

3. Unit Testing and Refactoring Techniques

  • State-based and interaction testing
  • How to break dependencies
  • Using stubs in Java
  • Using mocks in Java
  • Isolation frameworks
  • Working with legacy code

4. Writing unit test code

  • Mapping test code to application code
  • Writing good test code
  • Arrange-act-assert unit test design pattern
  • Creating a fake object dynamically
  • Building a test API

5. Organizing and Executing Unit Tests

  • Using hierarchies and automation
  • Organizing, automating and executing
  • Measurement of unit testing goodness

6. Test-Driven Development (TDD)

  • TDD core principles and techniques
  • How to decide whether TDD is a good investment
  • TDD tools

7. Unit Testing Frameworks and Tools

  • Unit testing frameworks: JUnit
  • Mocking frameworks case: Mockito
  • Execution environments

Seattle, San Francisco, Chicago, Boston, New York, Austin (USA) · Vancouver, Toronto, Montreal (Canada) · Mexico City (Mexico) · Rio de Janeiro, Sao Paulo (Brazil) · Santiago (Chile) · Stockholm (Sweden) · Copenhagen (Denmark) · Dublin (Ireland) · London (UK) · Paris, Toulouse, Lyon, Nice (France) · Amsterdam, Eindhoven (Netherlands) · Brussels (Belgium) · Berlin, Munich (Germany) · Helsinki (Finland) · Tallinn (Estonia) · Zurich (Switzerland) · Vienna (Austria) · Prague (Czech Republic) · Warsaw (Poland) · Milan Rome (Italy) · Barcelona, Madrid, Malaga (Spain) · Lisbon (Portugal) · Moscow, St Petersburg (Russian Federation) · Cape Town, Johannesburg (South Africa) · Nairobi (Kenya) · Tel Aviv (Israel) · Riyadh (Saudi Arabia) · Dubai (UAE) · Doha (Qatar) · Delhi, Pune, Hyderabad, Bengaluru (India) · Kuala Lumpur (Malaysia) · Singapore · Jakarta (Indonesia) · Ho Chi Minh City (Vietnam) · Seoul (South Korea) · Beijing, Shanghai (China) · Hong Kong · Tokyo (Japan) · Sydney, Melbourne (Australia) · Auckland (New Zealand)