Update test documentation with examples

[minhhoang1023]

This PR updates the existing documentation by including examples on how to build test. This is so that users can easily replicate, and hence reduce the barrier to contributing. Some guidelines on how to fix failed existing tests also included

Instructions were provided for:

• View test
• Model test
• Controller test

Big thanks to @Chavithra for the help

Description

• Summary of the change / bug fix.
• Link # issue, if applicable.
• Screenshot of the feature or the bug before/after fix, if applicable.
• Relevant motivation and context.
• List any dependencies that are required for this change.

How has this been tested?

• Please describe the tests that you ran to verify your changes.
• Provide instructions so we can reproduce.
• Please also list any relevant details for your test configuration.

Checklist:

• Update our Hugo documentation following these guidelines.
• Update our tests following these guidelines.
• Make sure you are following our CONTRIBUTING guidelines.
• If a feature was added make sure to add it to the corresponding scripts file.

Others

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My code passes all the checks pylint, flake8, black, ... To speed up development you should run pre-commit install.
• New and existing unit tests pass locally with my changes. You can test this locally using pytest tests/....

[Chavithra]

That's great.

Thanks Minh !