[Gambas-user] Test Module, First try
chrisml at deganius.de
Tue Jul 21 11:38:14 CEST 2020
Am 20.07.20 um 14:40 schrieb Brian G:
> Thanks, That was a great explanation of what happens when you remove
> a test module, Maybe that could be in the documentation?
Maybe it lacks an explanation what gb.test really does:
It runs the tests (Assert.*) which can access all the public available
interfaces of the project at runtime *from inside the project*.
The tests are organized as little programs (testmethods) which again can
be organized in testmodules and testsuites at the end.
A testsuite is nothing other that a string which contains the names of
the testmodules and testmethods to be executed. gb.test takes this
string and executes all tests which are defined by it. By default (if
the string is empty) gb.test executes all testmodules and the included
testmethods it finds in the project. The execution order is always
alphabetically by the names of the testmodules and testmethods.
So it is natural, that a deleted (or nonexistent) testmethod or
testmodule which is called by the testsuite crashes the system.
> Ok so your previous email talks about not monitoring string returned
> when testing for errors. I am retrofitting the tests to a system
> which only returns string as errors, or raises and error when they
> If I want to test that the internal modules are returning the correct
> error in different situations, what would/should be the correct model
> to use when using the test harness to test this App. And I would like
> to emphasize check that the correct error is returned.
> Should the modules return an error code, then print the actual text
> thru another function in order to separate the module functionality
> from the displayed text? This would imply that it's difficult to
> throw errors anymore as error.raise does not seem to allow a code to
> be passed. I don't really understand how to re-implement error
> handling such that it will fit nicely with the test suite.
As long as you control the errors inside the tested project in this way:
Error.Raise("My error description")
... IMO* it is no problem, it is fully reliable. You can test with:
' create the error situation and then test it:
Assert.Error("My error description")
* I said IMO because I am unsure when the translation of errors happen
if the project is internationalized and has translated error strings. We
would have to ask Benoît for that or try it out. In that case you had to
Assert.Error(("My error description"))
But if you rely on error message strings of the interpreter or any other
component or program, as you did in the case I mentioned**, you have to
be aware that it could have been altered or translated.
** You tried to test the non-existence of a component by testing for an
error string of the interpreter, as I remember. But in reality *you
tested the error string of the interpreter* and not *whether or not the
> I had a great Sunday, I was off hiking in the mountains, did a 16
> mile section of the high Sierra trail, so cool the whole thing is
> above 10,000 feet(3048 meters).
Wow, cool, that sounds beautiful! :-)
Dies ist keine Signatur
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the User