You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 1-intro-to-unit-tests.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,11 +120,11 @@ This is much clearer. We immediately have an idea of what could be going wrong a
120
120
121
121
### Challenge 2: Unit test bad practices
122
122
123
-
Take a look at [1-into-to-unit-tests/challenge-2](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/1-into-to-unit-tests/challenge-2) in the exercises repository.
123
+
Take a look at [1-into-to-unit-tests/challenge](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/1-into-to-unit-tests/challenge) in the exercises repository.
124
124
125
125
:::::::::::::::::::::::::::::::: solution
126
126
127
-
A solution is provided in [episodes/1-into-to-unit-tests/challenge-2/test/solution](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/1-into-to-unit-tests/challenge-2/test/solution).
127
+
A solution is provided in [1-into-to-unit-tests/solution](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/1-into-to-unit-tests/solution).
Copy file name to clipboardExpand all lines: 2-intro-to-fortran-unit-tests.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,11 +43,11 @@ Various bad practices can make it difficult to unit test Fortran including...
43
43
44
44
#### Challenge 1: Identify bad practice for unit testing Fortran
45
45
46
-
Take a look at [2-intro-to-fortran-unit-tests/challenge-1/challenge](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/2-intro-to-fortran-unit-tests/challenge-1/challenge) in the exercises repository.
46
+
Take a look at [2-intro-to-fortran-unit-tests/challenge](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/2-intro-to-fortran-unit-tests/challenge) in the exercises repository.
47
47
48
48
:::::::::::::::::::::::::::::::: solution
49
49
50
-
A solution is provided in [2-intro-to-fortran-unit-tests/challenge-1/solution](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/2-intro-to-fortran-unit-tests/challenge-1/solution).
50
+
A solution is provided in [2-intro-to-fortran-unit-tests/solution](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/2-intro-to-fortran-unit-tests/solution).
Copy file name to clipboardExpand all lines: 3-fortran-unit-test-syntax.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -357,11 +357,11 @@ end function my_test_params_toString
357
357
358
358
## Challenge: Write Fortran unit tests in multiple frameworks.
359
359
360
-
Take a look at [3-fortran-unit-test-syntax/challenge-1/challenge](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/3-fortran-unit-test-syntax/challenge-1/challenge).
360
+
Take a look at [3-fortran-unit-test-syntax/challenge](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/3-fortran-unit-test-syntax/challenge).
361
361
362
362
:::::::::::::::::::::::::::::::: solution
363
363
364
-
A solution is provided in [3-fortran-unit-test-syntax/challenge-1/solution](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/3-fortran-unit-test-syntax/challenge-1/solution).
364
+
A solution is provided in [3-fortran-unit-test-syntax/solution](https://github.com/UCL-ARC/fortran-unit-testing-exercises/tree/main/episodes/3-fortran-unit-test-syntax/solution).
0 commit comments