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

' Gambas test file


' A Test with no message, should display then method name as message

Public Sub NoMessage()

    'There is no message whicht
    Assert.Ok(True)

End

Public Sub NoMessageInbetween()

    Assert.Ok(True, "TestNoMessageInbetween Assert 1 description defined")
    Assert.Ok(True)
    Assert.Ok(True, "Assert 3 description defined")
    Assert.Ok(True)

End

Public Sub Note()

    Test.Note("This\nis\na\nnote")
    Test.SkipAll()

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`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00

			`' A Test with no message, should display then method name as message`

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 NoMessage()`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00
			`'There is no message whicht`
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.Ok(True)`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00
			`End`

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 NoMessageInbetween()`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00
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.Ok(True, "TestNoMessageInbetween Assert 1 description defined")`
			`Assert.Ok(True)`
			`Assert.Ok(True, "Assert 3 description defined")`
			`Assert.Ok(True)`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00
			`End`

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 Note()`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00
Fix: Free Assert from non-assertions Assert free from non-assertions. Also Assert and Test now are modules. 2020-04-27 12:01:47 +02:00			`Test.Note("This\nis\na\nnote")`
			`Test.SkipAll()`
gb.test: Refactoring and improvements [GB.TEST] * NEW: Assert some reworking, skip, todo and body removed * NEW: in a testcontainer in _new the count of tests can be defined by Me.Plan and differences between assertions counted and planned lead to No success * NEW: Unittest.Bailout 2019-12-30 22:10:37 +01:00
			`End`