gambas-source-code/main/lib/test/gb.test/.src/TestMyself/TError.test

' Gambas test file

Public Sub Error()

    Dim a As Long

    Try a = 3 / 0
    Assert.Error("Wanted error. Ok if ok.")

    Try a = 3 / 0 ' Throws Error.Code 26
    Assert.ErrorCode(26, "Wanted error 26. Ok if ok.")

End
gb.test refactoring for use of test modules [GB.TEST] * NEW: Add support for test modules. 2020-02-23 12:38:53 +01:00			`' Gambas test file`
new component gb.test [GB.TEST] * NEW: component for unittesting 2019-11-15 22:33:54 +01:00
gb.test rename test modules [GB.TEST] * OPT: rename testmodules and methods in them, get rid of such a lot "Test" 2020-05-26 20:45:18 +02:00			`Public Sub Error()`
new component gb.test [GB.TEST] * NEW: component for unittesting 2019-11-15 22:33:54 +01:00
			`Dim a As Long`

			`Try a = 3 / 0`
			`Assert.Error("Wanted error. Ok if ok.")`

			`Try a = 3 / 0 ' Throws Error.Code 26`
gb.test: Use gb.test.tap [GB.TEST] * NEW: Use gb.test. This removes the Assert and Track classes and uses gb.test.tap instead. Test methods are now executed inside subtests, plan lines are auto- matically emitted by the harness. Differences between gb.tests's and gb.test.tap's Assert module: - Instead of Assert.True and Assert.False, use Assert.Ok. - Instead of Assert.Equals* for every type, there is a generic Assert.Equals for Variants and a specific Assert.StringEquals for strings which prints diagnostics when the test fails. - Assert.BailOut does not terminate the entire program, just the TAP stream. - Assert.ErrorWithCode is called Assert.ErrorCode. All TAP printing is done through Assert now. Errors happening in the test code are not caught and spoofed in the TAP stream anymore, they cause a test failure. The system would be more robust if the testee would be in a different process from the tester. 2020-02-24 17:59:14 +01:00			`Assert.ErrorCode(26, "Wanted error 26. Ok if ok.")`
new component gb.test [GB.TEST] * NEW: component for unittesting 2019-11-15 22:33:54 +01:00
			`End`