DiscoverNo CompromisesShould you change application code to support a test?
Should you change application code to support a test?

Should you change application code to support a test?

Update: 2024-03-05
Share

Description

When you're writing a test it can be so tempting to just "tweak" some app code to make it easier to write that test, but we discuss why that might not be a good idea. We also talk about some app changes while writing tests that are beneficial to the overall project.

  • (00:00 ) - Sometimes changing code makes testing easier

  • (01:30 ) - Different types of code changes

  • (02:45 ) - An example with Laravel jobs

  • (04:30 ) - A time when it's okay to change code while testing

  • (08:50 ) - Avoid problems by writing tests earlier

  • (09:30 ) - Silly bit


Don't "compromise" on testing. See how we can help level up your Laravel project.
Comments 
00:00
00:00
1.0x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Should you change application code to support a test?

Should you change application code to support a test?

Joel Clermont and Aaron Saray