Improve testing docs

[gpsaggese]

My approach is to start testing end-to-end behaviors and then go towards the inner working. We don't want to test implementation details, otherwise the maintenance cost is insane.

This looks like testing too details.

Also we don't want to test that OpenAI specific stuff. E.g., we don't have to test that OpenAI follows its own API.

Can you start adding some of these suggestions to the unit test docs? ./docs/tools/unit_test/all.run_unit_tests.how_to_guide.md ./docs/tools/unit_test/all.write_unit_tests.how_to_guide.md

I'll file a bug

@gpsaggese Could you please file and assign the bug to me? I’ll work on it from there and resolve this conversation.

Originally posted by @srinivassaitangudu in https://github.com/causify-ai/helpers/pull/777#discussion_r2134067084

[srinivassaitangudu]

@gpsaggese please review PR #840 .

[gpsaggese]

• [ ] Let's do a top-to-bottom review of both documents
  • [ ] @srinivassaitangudu
  • [ ] @Shaunak01
  • [ ] @tkpratardan
• [ ] Publish it as blog

[gpsaggese]

@srinivassaitangudu let's start with the review so we can write the blog entry and update the white paper

[srinivassaitangudu]

Sure Gp.