Dependencies upgrade for Pharo 13

• Dependencies upgrade for Pharo 13
• Tonel format update

thanks to @oliveiraallex

v7.0.3

What's Changed

• Add Pharo12 into CI by @dionisiydk in #40
• Pharo 13 support. Pharo 11- support dropped by @JanBliznicenko in #43

Full Changelog: v7.0.2...v7.0.3

Pharo 11 compatibility

v7.0.2

Exclude Help from baseline (unsupported in Pharo11)

Update Ghost for debugger fixes

v7.0.1

Update Ghost for debugger fixes

Pharo 10 compatibility

v7.0.0

Fix baseline

Last version for Pharo <= 9

• CI is migrated to github actions
• Tests fixed to be compatible for Pharo 10 and 11
• CI for Pharo 9 , 10 and 11

Compatibility with Pharo 9

Updates for compatibility with current development version of Pharo 9 related to TestEnvironment changes. The fix is compatible with Pharo 8 and 7 as well.

Thanks @JanBliznicenko

Mark baseline that project is metadataless

From @jecisc :
This allows Metacello to better know the current version of the github project and not reload it when the right version is already in the image.
On a project with a lot of dependencies, it tries to load Mocketry around 40 times because this support is not there I think. Because I have multiple projects depending on Mocketry and for each project transitively depending on it, it tries to load it...

Prevent user mistakes with missing #stub message

Expectation methods (teacher API) are marked with pragma . Such methods are not allowed to be send to mocks to prevent user mistakes when it forget #stub message with defining an expectation for a mock.
So now following examples will fail with explicit error:

mock someMessage willReturn: 1.
mock will: [2].
mock stub willRaise: Error new

New should expression #takeAWhile and more

• New should expression is supported for behaviour validation:

[mock someMessage] fork.
mock should takeAWhile to receive someMessage.

• Better validation of argument capture. Now the validation result knows that the subject was captured from concrete message send.
• API for validation of all involved objects are changed.
  Following expressions are not anymore supported:

Any should receive someMessage.
(Kind of: Point) should receive someMessage

Now extra #inTest message is required:

Any inTest should receive someMessage.
(Kind of: Point) inTest should receive someMessage

In next version the "class word" based DSL will be deprecated by "Any expressions" :

Any object inTest should receive someMessage
(Any instanceOf: Point) inTest should receive someMessage.
(Any kindOf: Number) inTest should be even.

• Better granularity of baseline: Core vs Tests. Core does not load any tests anymore (fixes #20).