22118 - Recent changes [en]

Runtime evaluation

WikiSysop — Fri, 24 Apr 2026 09:06:07 GMT

Exercises to be handed in

← Older revision		Revision as of 11:06, 24 April 2026
(5 intermediate revisions by the same user not shown)
Line 85:		Line 85:
	== Exercises to be handed in ==		== Exercises to be handed in ==
	"Calculate" can mean many things here; Analyze, argue, explain, show, or even demonstrate. For some algorithms (not these) it even means "do a lot of math". The calculation must be convincingly explained based on reasoning. Just showing the result is insufficient.<br>		"Calculate" can mean many things here; Analyze, argue, explain, show, or even demonstrate. For some algorithms (not these) it even means "do a lot of math". The calculation must be convincingly explained based on reasoning. Just showing the result is insufficient.<br>
	# Calculate Big O of exercise 2 in [[~~Python Recap and Objects~~]]		# Calculate Big O of exercise 2 in [[Solo git]]
	# Calculate Big O of exercise 1 in [[~~Regular Expressions~~]]		# Calculate Big O of exercise 1 in [[Functions, namespace, memory management]]
	# Calculate Big O of exercise 2 in [[~~Regular Expressions~~]]		# Calculate Big O of exercise 3 in [[Functions, namespace, memory management]]
	# Calculate Big O of exercise 5 in [[~~Regular Expressions~~]]		# Calculate Big O of exercise 1 in [[Comprehension, generators, iteration]]
	# Calculate Big O of exercise 9 in [[~~Regular Expressions~~]]		# Calculate Big O of exercise 3 in [[Comprehension, generators, iteration]]
	# Calculate Big O of exercise 9 in [[~~Making Functions~~]]		# Calculate Big O of exercise 6 in [[Comprehension, generators, iteration]]
	# ~~Calculate Big O~~ of ~~exercise 1 in~~ [[~~Advanced Data Structures and New Data Types~~]]		# Analyze the algorithm of [[QT clustering]] (see Details). Make an argument for what is the worst case running time in the described form. This will be hard. The "Add one point from your data set at a time in such a way that you extend the candidate cluster diameter the least" covers an algorithm that you must think up. You might benefit from making some simple pseudo code of the entire QT clustering algorithm.
	~~# Calculate Big O of exercise 4~~ in ~~[[Advanced Data Structures and New Data Types]]~~
	~~# Calculate Big O~~ of ~~exercise 6 in [[Comprehension, Generators, Functions and Methods]]~~

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

Intermediate unit test

WikiSysop — Sun, 19 Apr 2026 18:15:44 GMT

Exercises to be handed in

← Older revision		Revision as of 20:15, 19 April 2026
(2 intermediate revisions by the same user not shown)
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.<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.

Beginning unit test

WikiSysop — Tue, 14 Apr 2026 16:37:28 GMT

Exercises to be handed in

← Older revision		Revision as of 18:37, 14 April 2026
(6 intermediate revisions by the same user not shown)
Line 20:		Line 20:
	which yptest		which yptest
	To install pytest, you need to be root/administrator.		To install pytest, you need to be root/administrator.
			# An install on a basic system
	pip install -U pytest		pip install -U pytest
	# or maybe (depending on your system)		# or maybe (depending on your system)
	sudo pip install -U pytest		sudo pip install -U pytest
			# Using ubuntu, which is also WSL in this situation, there is a package
			apt install python3-pytest

	== Subjects covered ==		== Subjects covered ==
Line 33:		Line 36:
	# Use your '''normalize''' function from exercise 3 in [[Functions, namespace, memory management]]. 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: a list of positive numbers, a list of negative numbers, a list of integers, a list of mixed floats and integers, a single number in the list, empty list, a list with at least one non-number (string, list, set), a set containing numbers, and a dict where the keys are numbers. Get other ideas if you can. The '''normalize''' function and all test functions must be in one single file (''normalize_test.py'' in ''unittest''), which you can run ''pytest'' on.<br><br>		# Use your '''normalize''' function from exercise 3 in [[Functions, namespace, memory management]]. 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: a list of positive numbers, a list of negative numbers, a list of integers, a list of mixed floats and integers, a single number in the list, empty list, a list with at least one non-number (string, list, set), a set containing numbers, and a dict where the keys are numbers. Get other ideas if you can. The '''normalize''' function and all test functions must be in one single file (''normalize_test.py'' in ''unittest''), which you can run ''pytest'' on.<br><br>
	# Now remove the '''normalize''' function from ''normalize_test.py'' and put it in its own file ''normalize.py''. Import it from the ''normalize_test.py'' like '''from normalize import normalize'''. The first ''normalize'' is the name of the .py file, the second ''normalize'' is the name of your normalize 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>		# Now remove the '''normalize''' function from ''normalize_test.py'' and put it in its own file ''normalize.py''. Import it from the ''normalize_test.py'' like '''from normalize import normalize'''. The first ''normalize'' is the name of the .py file, the second ''normalize'' is the name of your normalize 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 ''normalize.py'' in ''unittest/src'' and ''normalize_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>		# 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 ''normalize.py'' in ''unittest/src'' and ''normalize_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 for how the search path works. Try to run the test from a different folder (unittest), like "pytest test/normalize_test.py" to see how vulnerable just using the path is.<br><br>
	# You hopefully remember the '''MyMath''' class you made in exercise 1 & 2 in [[Beginning classes]]. Make a folder ''classes'' in your ''unittest/src'' folder and put the ''MyMath'' class in a file ''MyMath.py'' in ''unittest/src/classes''. Now make a unit test file ''MyMath_factorial_test.py'' in ''unittest/test'' that - surprise - tests your factorial method. Test it with at least these input: 12, 2, 1, 0, -1, 3.0, 3.4, "3", "3.1.", "ABC". Parametrize at least the tests that should succeed. Bonus for parametrizing the exceptions.		# You hopefully remember the '''MyMath''' class you made in exercise 1 & 2 in [[Beginning classes]]. Make a folder ''classes'' in your ''unittest/src'' folder and put the ''MyMath'' class in a file ''MyMath.py'' in ''unittest/src/classes''. Now make a unit test file ''MyMath_factorial_test.py'' in ''unittest/test'' that - surprise - tests your factorial method. Test it with at least these input: 12, 2, 1, 0, -1, 3.0, 3.4, "3", "3.1.", "ABC". Parametrize at least the tests that should succeed. Bonus for parametrizing the exceptions.<br><br>
			# ''MyMath'' class also contains the ''supply'' method. Make unit tests for that method in the file ''unittest/test/MyMath_supply_test.py''. Make the "usual" tests, which are the same as you did in the first exercise.<br><br>
			# Now make unit tests for the ''average'' method in '''MyMath'''. Make the tests in the file ''unittest/test/MyMath_average_test.py''. Notice how that interacts with the ''supply'' unit tests because ''average'' depends on correct working of ''supply''. Sometimes you won't even find the flaw in one method before you test another that depends on it. I am not going to tell you this time what unit tests you should make. You should know by now.

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

Intermediate unit test

WikiSysop — Tue, 14 Apr 2026 14:35:42 GMT

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.

Beginning unit test

WikiSysop — Tue, 14 Apr 2026 14:35:31 GMT

Exercises for extra practice

← Older revision		Revision as of 16:35, 14 April 2026
(3 intermediate revisions by the same user not shown)
Line 34:		Line 34:
	# Now remove the '''normalize''' function from ''normalize_test.py'' and put it in its own file ''normalize.py''. Import it from the ''normalize_test.py'' like '''from normalize import normalize'''. The first ''normalize'' is the name of the .py file, the second ''normalize'' is the name of your normalize 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>		# Now remove the '''normalize''' function from ''normalize_test.py'' and put it in its own file ''normalize.py''. Import it from the ''normalize_test.py'' like '''from normalize import normalize'''. The first ''normalize'' is the name of the .py file, the second ''normalize'' is the name of your normalize 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 ''normalize.py'' in ''unittest/src'' and ''normalize_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>		# 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 ''normalize.py'' in ''unittest/src'' and ''normalize_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>
			# You hopefully remember the '''MyMath''' class you made in exercise 1 & 2 in [[Beginning classes]]. Make a folder ''classes'' in your ''unittest/src'' folder and put the ''MyMath'' class in a file ''MyMath.py'' in ''unittest/src/classes''. Now make a unit test file ''MyMath_factorial_test.py'' in ''unittest/test'' that - surprise - tests your factorial method. Test it with at least these input: 12, 2, 1, 0, -1, 3.0, 3.4, "3", "3.1.", "ABC". Parametrize at least the tests that should succeed. Bonus for parametrizing the exceptions.

	== 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.~~

Intermediate unit test

WikiSysop — Tue, 14 Apr 2026 14:16:24 GMT

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 ==

Beginning unit test

WikiSysop — Tue, 14 Apr 2026 14:15:55 GMT

Exercises to be handed in

← Older revision		Revision as of 16:15, 14 April 2026
(4 intermediate revisions by the same user not shown)
Line 9:		Line 9:
	Resource: [[Example code - Unit test]]<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>

			=== Installation of pytest ===
			If you are using an anaconda python installation pytest is included. You can test in your python has pytest.
			# On command line both should work or none
			python3 -c "import pytest"
			which pytest
			# It is pretty clear if you fail. Success can be more obscure.
			# Here is a fail test, so you can compare
			python3 -c "import yptest"
			which yptest
			To install pytest, you need to be root/administrator.
			pip install -U pytest
			# or maybe (depending on your system)
			sudo pip install -U pytest

	== Subjects covered ==		== Subjects covered ==
Line 15:		Line 29:

	== 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.<br>
	# 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>		In some of these exercise you need to hand in not just a single file, but multiple files in a folder hierarchy. Zip the folder structure for your entire solution folder. Make sure it is clear to see what exercise your code/data is solving. And learn to zip :-)
	# 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>		# Use your '''normalize''' function from exercise 3 in [[Functions, namespace, memory management]]. 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: a list of positive numbers, a list of negative numbers, a list of integers, a list of mixed floats and integers, a single number in the list, empty list, a list with at least one non-number (string, list, set), a set containing numbers, and a dict where the keys are numbers. Get other ideas if you can. The '''normalize''' function and all test functions must be in one single file (''normalize_test.py'' in ''unittest''), which you can run ''pytest'' on.<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>		# Now remove the '''normalize''' function from ''normalize_test.py'' and put it in its own file ''normalize.py''. Import it from the ''normalize_test.py'' like '''from normalize import normalize'''. The first ''normalize'' is the name of the .py file, the second ''normalize'' is the name of your normalize 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>
	# 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>		# 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 ''normalize.py'' in ''unittest/src'' and ''normalize_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>
	~~# 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.

Intermediate unit test

WikiSysop — Fri, 10 Apr 2026 12:07:43 GMT

Subjects covered

← Older revision		Revision as of 14:07, 10 April 2026
(2 intermediate revisions by the same user not shown)
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 ==
	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.~~