🐅 Epic: Implement Testing in Ersilia

[DhanshreeA]

Summary

We want to implement testing in Ersilia at several levels such as "unit testing" and "integration testing" in the core ersilia codebase. We have two test model repositories created to act as fixtures for these tests.

Objectives

• Unit tests for the CLI - Ideally tests for all modules across the codebase. 🐕 Batch: Unit Testing in Ersilia CLI #1319
• Integration tests for the CLI - End to end testing of all interfaces across Ersilia to fetch, and serve a model.

Documentation

[GemmaTuron]

Hi @DhanshreeA

This issue is not well described. Either add information or close it if it is no longer in use

[DhanshreeA]

I will update this as we very much want to achieve this still.

[GemmaTuron]

@DhanshreeA how is this related to #1319 ?

[DhanshreeA]

@GemmaTuron I have updated the issue description by attaching #1319 to the unit testing task. Basically we are identifying individual test cases and tracking them in the unit testing batch.

[DhanshreeA]

@Abellegese could you also document your test cases here by linking relevant commits/PR?

[Abellegese]

So this issue has been addressed in the following cases:

1. Pytest for five ersilia CLI and all the associated function level testing using partial mocking.
   • Issue: 🐕 Batch: A more comprehensive PyTest pipeline #1368 @DhanshreeA this needs to be closed.
   • PR: Pytest CLI test using partial mocking #1397
2. Playground test: to test model behaviour using custom rules
   • Issue: 🐕 Batch: A more comprehensive PyTest pipeline #1368
   • PR: CLI test integration #1383
3. Model Tester: To test and remote and local models
   • PR: Model tester and Inspect command functionality updates #1416

[miquelduranfrigola]

Good. @DhanshreeA I believe this is good to be closed?