luisgulo/gambas-source-code
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
gambas-source-code/comp/src/gb.test/.src/TestMyself/TestInternals.test

80 lines
3 KiB
Text
Raw Normal View History

TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
' Gambas test file
'' P
Public Sub ParseTestCommands()
Dim sCommand As String
Dim Commands As TestCommand[]
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
Dim sGot As String
Dim iGot As Integer
gb.test: new function Test.GetAllTests [GB.TEST] * New: Test.GetAllTests returns a collection of all testmodules and their testmethods
2020-05-11 23:28:42 +02:00
TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
'Three TestModules
sCommand = "Bing, Bong, Bung"
Commands = TestCommand.ParseCommands(sCommand)
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
sGot = Commands[0].ModuleName & Commands[1].ModuleName & Commands[2].ModuleName
gb.test: new function Test.GetAllTests [GB.TEST] * New: Test.GetAllTests returns a collection of all testmodules and their testmethods
2020-05-11 23:28:42 +02:00
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
Assert.Equals(sGot, "BingBongBung", "ParseCommands: Three testmodules")
gb.test: new function Test.GetAllTests [GB.TEST] * New: Test.GetAllTests returns a collection of all testmodules and their testmethods
2020-05-11 23:28:42 +02:00
TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
'Test testmodules sort
sCommand = "Bing,Bung,Bong"
Commands = TestCommand.ParseCommands(sCommand)
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
sGot = Commands[0].ModuleName & Commands[1].ModuleName & Commands[2].ModuleName
gb.test: new function Test.GetAllTests [GB.TEST] * New: Test.GetAllTests returns a collection of all testmodules and their testmethods
2020-05-11 23:28:42 +02:00
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
Assert.Equals(sGot, "BingBongBung", "ParseCommands: Testmodules have to be sorted")
TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
'Three testmodules, one with three methods
sCommand = "Bong.B, Bing, Bong.A, Bung, Bong.C"
TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
Commands = TestCommand.ParseCommands(sCommand)
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
sGot = Commands[0].ModuleName & Commands[1].ModuleName & Commands[2].ModuleName
Assert.Equals(sGot, "BingBongBung", "ParseCommands: Three testmodules, one with three methods")
gb.test: new function Test.GetAllTests [GB.TEST] * New: Test.GetAllTests returns a collection of all testmodules and their testmethods
2020-05-11 23:28:42 +02:00
TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
'Methods name sort
TestCommand parsing done, but system still buggy Without "Debug oTest.Name" in TestSuite.class:39 it would silently crash anywhere after TestNoMessage is done without printing any single character. Reason is "Assert.BailOut" in TestSuite:51 which miraculously does nothing. If the testsystem itself crashes, ist must print "BailOut ..." But here also can be seen, why the system has to print every assertion immediately. Any bufferíng is bad because if the testsystem crashes the buffered results are gone. So we must get rid of the buffered stream thing and go back to Print scattered all over ;-)
2020-04-08 12:39:55 +02:00
sGot = Commands[1].Methods.Join()
Assert.Equals(sGot, "A,B,C", "ParseCommands: Methods name sort")
'Three testmodules, one with methods, but Bong also wanted all, the more greedy one has to get it
sCommand = "Bong, Bing, Bong.A, Bung, Bong.B, Bong.C"
Commands = TestCommand.ParseCommands(sCommand)
'Methods name sort
iGot = Commands[1].Methods.Count
Assert.Equals(iGot, 0, "ParseCommands: Greedy testmodule Bong")
'Programmer was a little tipsy but got it all except Bung which only wants testmethod U
sCommand = "Bong, Bong.A, Bing, Bing, Bing, Bing, Bing, Bing, Bong.A, Bung.U, Bong.B, Bong.C, Bing, Bing, Bing, Bong, Bong"
Commands = TestCommand.ParseCommands(sCommand)
'Methods name sort
iGot = Commands[0].Methods.Count
Assert.Equals(iGot, 0, "ParseCommands: Tipsy programmer 1")
iGot = Commands[1].Methods.Count
Assert.Equals(iGot, 0, "ParseCommands: Tipsy programmer 2")
iGot = Commands[2].Methods.Count
Assert.Equals(iGot, 1, "ParseCommands: Tipsy programmer 3")
sGot = Commands[2].Methods[0]
Assert.Equals(sGot, "U", "ParseCommands: Tipsy programmer 4")
TestCommand Parser Parses the string that containes testmodules and -methods. The parser is tested in TestInternals.
2020-04-08 00:40:14 +02:00
End
gb.test: new function Test.GetAllTests [GB.TEST] * New: Test.GetAllTests returns a collection of all testmodules and their testmethods
2020-05-11 23:28:42 +02:00
'' Tests the ability to return all tests
'' in the project as a collection
Public Sub ReflectTest()
Dim tests As Collection
tests = Test.GetAllTests()
'count of all testmodules, if it fails we created a new one and we have to count new
Assert.Equals(tests.Count, 10, "number of all testmodules")
'count of all testmethods, if it fails we created a new one and we have to count new
Assert.Equals(tests["TestAllAsserts"].Count, 13, "count of all testmethods in TestAllAsserts")
Assert.Equals(tests["TestBailout"].Count, 1, "count of all testmethods in TestBailout")
Assert.Equals(tests["TestCrashes"].Count, 2, "count of all testmethods in TestCrashes")
Assert.Equals(tests["TestElse"].Count, 3, "count of all testmethods in TestElse")
Assert.Equals(tests["TestEmpty"].Count, 0, "count of all testmethods in TestEmpty")
End
Reference in a new issue Copy permalink