Update exercise

Author: IshaanDesai

05_testing_and_ci/python_testing_exercise.md

@@ -2,9 +2,8 @@
 
 ## Starting Remarks
 
-- [Exercise repository link](https://github.com/Simulation-Software-Engineering/testing-python-exercise-wt2223)
-- Deadline for submitting this exercise is **Thursday 26th January 2023 09:00**.
-- Structure all the tests in a format similar to what is shown in the [demo code](https://github.com/Simulation-Software-Engineering/Lecture-Material/blob/main/05_testing_and_ci/examples/python_testing).
+- [Exercise repository link](https://github.com/Simulation-Software-Engineering/testing-python-exercise-wt2425)
+- Deadline for submitting this exercise is **Wednesday 22nd January 2025 09:00**.
 
 ## Prerequisites
 
@@ -18,11 +17,11 @@
     - [pytest](https://docs.pytest.org/en/6.2.x/getting-started.html#install-pytest)
     - [unittest](https://docs.python.org/3/library/unittest.html#module-unittest)
     - [coverage](https://coverage.readthedocs.io/en/6.2/#quick-start)
-    - [tox](https://tox.wiki/en/4.0.15/installation.html)
+    - [tox](https://tox.wiki/en/4.23.2/installation.html)
 
 ## Step 1 - Getting Familiar With the Code
 
-- Fork the [repository](https://github.com/Simulation-Software-Engineering/testing-python-exercise-wt2223).
+- Fork the [repository](https://github.com/Simulation-Software-Engineering/testing-python-exercise-wt2425).
 - The code in `diffusion2d.py` is in principle the same code used for the Python packaging exercise. The main difference is that now the code has a class `SolveDiffusion2D` which has several member functions.
 - Each function name states what the function does, for example the function `initialize_domain()` takes in input arguments `w` (width), `h` (height), `dx` and `dy` and sets the values to member variables of the class and also calculates the number of points in x and y directions.
 - The functions `initialize_domain` and `initialize_physical_parameters` have default values for all input parameters, hence they can be called without any parameters.
@@ -51,7 +50,7 @@
     - Note that you have the object of the class `SolveDiffusion2D` and hence you can access member variables, for example `solver.nx` and `solver.ny`. This is useful to check the actual values.
 - Using a similar workflow, complete the other two unit tests.
 - Run the tests using `pytest`.
-- It is observed that in some instances `pytest` is not able to find the tests. One reason is the way pytest is installed, which is typically either using `pip` or `apt`. Refer to the [corresponding section](https://github.com/Simulation-Software-Engineering/Lecture-Material/blob/main/05_testing_and_ci/python_testing_demo.md#pytest) in the demo for more details. If such errors occur, then try to explicitly point pytest to the relevant test file. For example:
+- It is observed that in some instances `pytest` is not able to find the tests. One reason is the way pytest is installed, which is typically either using `pip` or `apt`. Refer to the [corresponding section](https://github.com/Simulation-Software-Engineering/Lecture-Material/blob/main/05_testing_and_ci/python_testing_demo.md#pytest) in the demo for more details. If such errors occur, then try to explicitly point pytest to the relevant test file in the following way:
 
 ```bash
 pytest tests/unit/test_diffusion2d_functions.py
@@ -103,9 +102,9 @@ pytest tests/unit/test_diffusion2d_functions.py
 
 ## Step 7 - Automation Using tox
 
-- Write a `tox.ini` file such that by running the command `tox`, both `pytest` and `unittest` are executed.
+- Write a `tox.toml` file such that by running the command `tox`, both `pytest` and `unittest` are executed.
 - Use the `requirements.txt` file to send all the dependencies information to tox.
 
 ## Step 8 - Submission
 
-- Open a pull request titled `Adding tests by <GitLab username>` from your fork to the main repository.
+- Open a pull request titled `[your GitLab username] Adding tests` from your fork to the main repository.