- Anything bigger than a unit test
- Anything bigger than a unit test
- Smaller than a UI test
- Anything bigger than a unit test
- Smaller than a UI test
- API level tests
- Writing tests takes too long - we don't have the time
- Writing tests takes too long - we don't have the time
- Code changes break the tests
- Writing tests takes too long - we don't have the time
- Code changes break the tests
- Our code is difficult to test
- Writing tests takes too long - we don't have the time
- Code changes break the tests
- Our code is difficult to test
- Anything else?
- Big changes are scary
- Many production issues
- Big changes are scary
- Many production issues
- Code not modular
- Big changes are scary
- Many production issues
- Code not modular
- Anything else?
- Make testing faster - you'll have the time
- Make testing faster - you'll have the time
- Make tests less coupled - fewer test changes
- Make testing faster - you'll have the time
- Make tests less coupled - fewer test changes
- Test the service - more confidence
- Refactoring is relaxing
- Releases are boring
- Refactoring is relaxing
- Releases are boring
- Code pride
- Adding an API test to core service
- Go to core service repo
- Checkout the branch TestingWorkshop
- Open MyTesla.CoreSvc.IntegrationTests\Controllers\VehicleControllerTests.cs
- Follow the example to add an API test
- Open this MyTesla.CoreSvc.IntegrationTests\Controllers\OrderControllerTests.cs
- Follow the example to add a happy path
- Add some sad path tests
CONS
- Slow to run
- Won't isolate issue
- Flakey
PROS
- Quick to write
- Not tied to code
- High confidence
- Start writing your own API tests
- Get these running in ATM
Made with Slides.com