Intermediate unit test - Revision history

WikiSysop: /* Exercises to be handed in */

2026-04-19T18:15:44Z

Exercises to be handed in

← Older revision		Revision as of 20:15, 19 April 2026
Line 20:		Line 20:
	# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>		# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>
	# Add unit tests for the method '''delete''' in your '''fasta''' class. Use a fixture for setting up a test set for you deletion tests. Hand in same way as above.<br><br>		# Add unit tests for the method '''delete''' in your '''fasta''' class. Use a fixture for setting up a test set for you deletion tests. Hand in same way as above.<br><br>
	# Change your unit test setup of your fasta class to the package structure. That includes the correct folder structure, pyproject.toml and __init__.py file.<br>br>		# Change your unit test setup of your fasta class to the package structure. That includes the correct folder structure, pyproject.toml and __init__.py file.<br><br>
	I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.		I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.

	== Exercises for extra practice ==		== Exercises for extra practice ==
	# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.		# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.

WikiSysop: /* Exercises to be handed in */

2026-04-19T18:15:36Z

Exercises to be handed in

← Older revision		Revision as of 20:15, 19 April 2026
Line 20:		Line 20:
	# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>		# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>
	# Add unit tests for the method '''delete''' in your '''fasta''' class. Use a fixture for setting up a test set for you deletion tests. Hand in same way as above.<br><br>		# Add unit tests for the method '''delete''' in your '''fasta''' class. Use a fixture for setting up a test set for you deletion tests. Hand in same way as above.<br><br>
	# Change your unit test setup of your fasta class to the package structure. That includes the correct folder structure, pyproject.toml and __init__.py file.		# Change your unit test setup of your fasta class to the package structure. That includes the correct folder structure, pyproject.toml and __init__.py file.<br>br>
	I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.		I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.

	== Exercises for extra practice ==		== Exercises for extra practice ==
	# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.		# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.

WikiSysop: /* Exercises to be handed in */

2026-04-19T17:58:41Z

Exercises to be handed in

← Older revision		Revision as of 19:58, 19 April 2026
Line 19:		Line 19:
	# Follow the file structure of having a ''code'' (or ''src'') folder for programs, a ''test'' folder for tests, and now a ''testdata'' folder for files containing test data. Now make unit tests and appropriate test data files for your '''fasta''' class from last week. In this exercise you just need to make unit test for the method '''load'''. You need to hand in both tests and test data.<br><br>		# Follow the file structure of having a ''code'' (or ''src'') folder for programs, a ''test'' folder for tests, and now a ''testdata'' folder for files containing test data. Now make unit tests and appropriate test data files for your '''fasta''' class from last week. In this exercise you just need to make unit test for the method '''load'''. You need to hand in both tests and test data.<br><br>
	# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>		# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>
	# Add unit tests for the method '''delete''' in your '''fasta''' class. Hand in same way as above.<br><br>		# Add unit tests for the method '''delete''' in your '''fasta''' class. Use a fixture for setting up a test set for you deletion tests. Hand in same way as above.<br><br>
			# Change your unit test setup of your fasta class to the package structure. That includes the correct folder structure, pyproject.toml and __init__.py file.
	I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.		I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.

	== Exercises for extra practice ==		== Exercises for extra practice ==
	# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.		# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.

WikiSysop: /* Exercises for extra practice */

2026-04-14T14:35:42Z

Exercises for extra practice

← Older revision		Revision as of 16:35, 14 April 2026
Line 23:		Line 23:

	== Exercises for extra practice ==		== Exercises for extra practice ==
			# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.

WikiSysop: /* Exercises to be handed in */

2026-04-14T14:16:24Z

Exercises to be handed in

← Older revision		Revision as of 16:16, 14 April 2026
Line 17:		Line 17:
	== Exercises to be handed in ==		== Exercises to be handed in ==
	You should make a special folder for the exercises. I will refer to my special folder as ''unittest'' in these exercises. You will also see some ''__pycache__'' folders appear in places. This is Pythons cache for "compiled" programs. It is safe to ignore and also to delete, because it may become outdated.		You should make a special folder for the exercises. I will refer to my special folder as ''unittest'' in these exercises. You will also see some ''__pycache__'' folders appear in places. This is Pythons cache for "compiled" programs. It is safe to ignore and also to delete, because it may become outdated.
			# Follow the file structure of having a ''code'' (or ''src'') folder for programs, a ''test'' folder for tests, and now a ''testdata'' folder for files containing test data. Now make unit tests and appropriate test data files for your '''fasta''' class from last week. In this exercise you just need to make unit test for the method '''load'''. You need to hand in both tests and test data.<br><br>
			# Add unit tests for the method '''save''' in your '''fasta''' class. Hand in same way as above.<br><br>
			# Add unit tests for the method '''delete''' in your '''fasta''' class. Hand in same way as above.<br><br>
			I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.

	== Exercises for extra practice ==		== Exercises for extra practice ==

WikiSysop: /* Subjects covered */

2026-04-10T12:07:43Z

Subjects covered

← Older revision		Revision as of 14:07, 10 April 2026
Line 11:		Line 11:

	== Subjects covered ==		== Subjects covered ==
	~~Overview of~~ test ~~methods~~<br>		Unit test using pytest framework.<br>
	~~Unit~~ test ~~using pytest framework.~~		Files, test data<br>
			Setting up real projects<br>

	== Exercises to be handed in ==		== Exercises to be handed in ==

WikiSysop: /* Exercises for extra practice */

2026-04-10T12:05:47Z

Exercises for extra practice

← Older revision		Revision as of 14:05, 10 April 2026
Line 18:		Line 18:

	== Exercises for extra practice ==		== Exercises for extra practice ==
	~~# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.~~

WikiSysop: /* Exercises to be handed in */

2026-04-10T12:05:35Z

Exercises to be handed in

← Older revision		Revision as of 14:05, 10 April 2026
Line 16:		Line 16:
	== Exercises to be handed in ==		== Exercises to be handed in ==
	You should make a special folder for the exercises. I will refer to my special folder as ''unittest'' in these exercises. You will also see some ''__pycache__'' folders appear in places. This is Pythons cache for "compiled" programs. It is safe to ignore and also to delete, because it may become outdated.		You should make a special folder for the exercises. I will refer to my special folder as ''unittest'' in these exercises. You will also see some ''__pycache__'' folders appear in places. This is Pythons cache for "compiled" programs. It is safe to ignore and also to delete, because it may become outdated.
	# Use your factorial function from exercise 2 in [[Making Functions]]. If you did not do so already, change it to use exceptions instead of '''sys.exit()''', when an error occurs. Now make simple unit tests for the following test cases: 12, 2, 1, 0, -1, 3.0, 3.4, "3", "3.1.", "ABC". The factorial function and all test functions must be in one single file (''factorial_test.py'' in ''unittest''), which you can run ''pytest'' on.<br><br>
	# Now remove the factorial function from ''factorial_test.py'' and put it in its own file ''factorial.py''. Import it from the ''factorial_test.py'' like '''from factorial import factorial'''. The first factorial is the name of the .py file, the second factorial is the name of your factorial function. Just run ''pytest'' (no file name) in the folder to check it works. It is more normal to have test and function separated.<br><br>
	# Above we removed test code from function code by creating two files. Next, put the files in their own folder in ''unittest''. I would put my ''factorial.py'' in ''unittest/src'' and ''factorial_test.py'' in ''unittest/test''. This way there is a very clear separation between function and test. The problem is making sure the test code loads the function code. Do it wrong a couple of times - it is very instructive.<br><br>
	# Follow the file structure of having a ''code'' (or ''src'') folder for programs, a ''test'' folder for tests, and now a ''testdata'' folder for files containing test data. Now make unit tests and appropriate test data files for your '''fasta''' class from last week. In this exercise you just need to make unit test for the method '''load'''. You need to hand in both tests and test data. Maybe you should zip it all. Learn to zip :-)<br><br>
	~~# Add unit tests for the method '''save''' in your '''fasta''' class.<br><br>~~
	~~# Add unit tests for the method '''delete''' in your '''fasta''' class.<br><br>~~
	~~I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.~~

	== Exercises for extra practice ==		== Exercises for extra practice ==
	# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.		# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.

WikiSysop: /* Required course material for the lesson */

2026-03-06T14:16:06Z

Required course material for the lesson

← Older revision		Revision as of 16:16, 6 March 2026
Line 7:		Line 7:
	Powerpoint: [https://teaching.healthtech.dtu.dk/material/22118/22118_09-Testing.ppt Testing]<br>		Powerpoint: [https://teaching.healthtech.dtu.dk/material/22118/22118_09-Testing.ppt Testing]<br>
	Online: [https://docs.pytest.org/ pytest documentation]<br>		Online: [https://docs.pytest.org/ pytest documentation]<br>
	~~Resource: [[Example code - Unit test]]<br>~~
	Resource: [[Unit test - start of reverse polish notation class]]<br>		Resource: [[Unit test - start of reverse polish notation class]]<br>
	Blog: [https://www.joelonsoftware.com/2000/04/30/top-five-wrong-reasons-you-dont-have-testers/ On testing], by the founder of StackExchange.<br>		Blog: [https://www.joelonsoftware.com/2000/04/30/top-five-wrong-reasons-you-dont-have-testers/ On testing], by the founder of StackExchange.<br>

WikiSysop: Created page with "NOTOC {| width=500 style="font-size: 10px; float:right; margin-left: 10px; margin-top: -56px;" |Previous: Beginning unit test |Next: Runtime evaluation |} == Required course material for the lesson == Powerpoint: [https://teaching.healthtech.dtu.dk/material/22118/22118_09-Testing.ppt Testing]
Online: [https://docs.pytest.org/ pytest documentation]
Resource: Example code - Unit test
Resource: Unit test - start of reverse polish notation clas..."

2026-03-06T14:15:39Z

Created page with "__NOTOC__ {| width=500 style="font-size: 10px; float:right; margin-left: 10px; margin-top: -56px;" |Previous: Beginning unit test |Next: Runtime evaluation |} == Required course material for the lesson == Powerpoint: [https://teaching.healthtech.dtu.dk/material/22118/22118_09-Testing.ppt Testing] Online: [https://docs.pytest.org/ pytest documentation] Resource: Example code - Unit test Resource: Unit test - start of reverse polish notation clas..."

New page

__NOTOC__
{| width=500 style="font-size: 10px; float:right; margin-left: 10px; margin-top: -56px;"
|Previous: [[Beginning unit test]]
|Next: [[Runtime evaluation]]
|}
== Required course material for the lesson ==
Powerpoint: [https://teaching.healthtech.dtu.dk/material/22118/22118_09-Testing.ppt Testing] 
Online: [https://docs.pytest.org/ pytest documentation] 
Resource: [[Example code - Unit test]] 
Resource: [[Unit test - start of reverse polish notation class]] 
Blog: [https://www.joelonsoftware.com/2000/04/30/top-five-wrong-reasons-you-dont-have-testers/ On testing], by the founder of StackExchange. 

== Subjects covered ==
Overview of test methods 
Unit test using pytest framework.

== Exercises to be handed in ==
You should make a special folder for the exercises. I will refer to my special folder as ''unittest'' in these exercises. You will also see some ''__pycache__'' folders appear in places. This is Pythons cache for "compiled" programs. It is safe to ignore and also to delete, because it may become outdated.
# Use your factorial function from exercise 2 in [[Making Functions]]. If you did not do so already, change it to use exceptions instead of '''sys.exit()''', when an error occurs. Now make simple unit tests for the following test cases: 12, 2, 1, 0, -1, 3.0, 3.4, "3", "3.1.", "ABC". The factorial function and all test functions must be in one single file (''factorial_test.py'' in ''unittest''), which you can run ''pytest'' on. 
# Now remove the factorial function from ''factorial_test.py'' and put it in its own file ''factorial.py''. Import it from the ''factorial_test.py'' like '''from factorial import factorial'''. The first factorial is the name of the .py file, the second factorial is the name of your factorial function. Just run ''pytest'' (no file name) in the folder to check it works. It is more normal to have test and function separated. 
# Above we removed test code from function code by creating two files. Next, put the files in their own folder in ''unittest''. I would put my ''factorial.py'' in ''unittest/src'' and ''factorial_test.py'' in ''unittest/test''. This way there is a very clear separation between function and test. The problem is making sure the test code loads the function code. Do it wrong a couple of times - it is very instructive. 
# Follow the file structure of having a ''code'' (or ''src'') folder for programs, a ''test'' folder for tests, and now a ''testdata'' folder for files containing test data. Now make unit tests and appropriate test data files for your '''fasta''' class from last week. In this exercise you just need to make unit test for the method '''load'''. You need to hand in both tests and test data. Maybe you should zip it all. Learn to zip :-) 
# Add unit tests for the method '''save''' in your '''fasta''' class. 
# Add unit tests for the method '''delete''' in your '''fasta''' class. 
I would not be surprised if you find errors in your '''fasta''' class based on these tests. I found flaws in my code.

== Exercises for extra practice ==
# Add unit tests for all methods in your '''fasta''' class. That will be a bit of work.