WCore testing engine

[Adrian Borucki]

WCore testing engine should be able to detect any erroneous behaviour of plug-ins and modules and it should be able to check if behaviour of WCore itself is correct, according to some earlier provided rules.

Result: WCore will be able to test plug-ins, modules and, to some extent, itself which is very useful for debugging purposes, especially that we can't run plug-ins or modules independently to check them.

[Jacky Alciné (jackyalcine)]

Define testing. Do you mean like searching for like unresolved symbols or perhaps unspecified but needed dependencies? Or do you mean a more structured sandbox, in a sense where we can allow users to enable permissions for specific plugins (i.e: network access, semantic access, file access, etc)?

[Adrian Borucki (gentoolx)]

Testing is comparing plug-in behaviour with expected test results - yes, searching for unresolved symbols counts for that.
The main purpose is enabling plug-ins and doing some earlier defined test sets - sending some signals, invoking methods, checking result values, checking exceptions etc. and reporting that (to a special log file or standard output). And this tool is needed for testing plug-ins because we can't run them independently.