re: Things Nobody Told Me About Being a Software Engineer VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Fun fact: someone taught me that early on in my career as a best practice to make sure that my tests were actually doing something. These days I t...
 
kyslik profile image Martin Kiesel twitter logo github logo
Permalink Report Abuse

Or delete some parts of the implementation and see if some tests fail. I sometimes split commits in test and implementation so I see failing pipeline.

THREAD
uzitech profile image Tony Brix twitter logo github logo
Permalink Report Abuse

My workflow is almost always:

  1. Write the code
  2. Write the test
  3. Run passing tests
  4. Comment out the code
  5. Run failing tests
  6. Uncomment code
THREAD
stealthmusic profile image Jan Wedel twitter logo github logo
Permalink Report Abuse

That’s why you should

  1. Write a failing test
  2. Make the test green by implementing
  3. Refactor Go back to 1.
REPLY
code of conduct - report abuse