This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.
Vítor Manuel de Morais Santos Costa 98f79484ae change throw mechanism to fit better with cleanup mechanism:
- balls are now stored off line and recovered by Prolog code when everything
is safe.
- if a ball exists, throw uses the *existing* one (be careful not to have one
laying around).
- Jump routine cleans up every cp except ones for setup_call handling, backtracking simply calls setup handlers.
2009-11-27 11:21:24 +00:00
..
2009-11-23 10:55:10 +00:00
2009-11-23 10:55:10 +00:00
2009-11-23 10:55:10 +00:00
2009-11-23 10:55:10 +00:00
2009-11-23 10:55:10 +00:00
2009-11-23 10:55:10 +00:00
2009-11-23 10:55:10 +00:00

Prolog Unit Tests
=================


---++ TBD

	* Add options to test units
		- Condition, setup, cleanup, blocked [OK]
	* Run the tests on make, etc.  [OK]
	* Report generation options

---++ What to do with loaded tests?

	* Keep them around
	* Remove them
	* Flag module as `volatile', so it is not saved.

---++ Distinguish user/system/library tests

---++ Deal with seperate test-files:

	* load_test_files(+Options)

---++ Volatile modules?

---++ Conversion of system tests:

	- test.pl internals [OK]
	- scripts called from test.pl [OK]
	- tests for packages

---++ Run tests concurrently?

	+ Tests applications for concurrent execution
	+ Saves time, notably on tests doing networking, timeout, etc.
	- Might be more complicated to understand

---++ Test wizard

	* Write tests to .plt files
	* Merge with existing content of .plt files
		- Read with comments and write back?

---++ Coverage analysis

	* See cover.pl