Minimum Viable Continuous Delivery

Private Methods

Testing private methods in software development sparks diverse opinions. Joe Zack argues that privacy is less critical, suggesting making methods public for testing ease. He believes that if a private method becomes necessary elsewhere, it should be public to facilitate shared behavior 1. Michael Outlaw, however, proposes a workaround by making methods protected and using mock classes for testing, though he admits it's a "super dirty" approach 2.

Privacy is dead. It's been dead for a long time. I just can't care that much anymore about access.

--- Joe Zack

This debate highlights the tension between maintaining encapsulation and ensuring testability.

   

Integration Testing

Integration testing is crucial in CI/CD pipelines, yet it presents unique challenges. Joe Zack shares his experience with creating integration tests to ensure proper key generation from cloud service objects 3. He suggests using test containers to simulate environments without needing full server setups, which simplifies testing infrastructure 4.

Test containers are a way to be able to do integration tests when you need infrastructure spun up just for that specific test.

--- Joe Zack

These strategies help streamline the testing process, ensuring reliability and efficiency in software development.