Refactor lexer tests to expose test function

[darylwright]

Summary

Use the example herehere to refactor the lexer tests so that the test function is exposed in those suites. This allows the IDE to detect tests for better integration and runnability. Also determine if Ava has native support for repeating tests on different data.

Other Information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[darylwright]

A major drawback of the approach in the struck through link is that all lexer assertions would be consolidated into a single test function, making it difficult to diagnose multiple lexer issues simultaneously. To that end, do not use the above example.

[darylwright]

It seems that using Ava's macros is the ideal approach here. We have the benefit of both reusing test implementation logic and being able to execute an individual test via the IDE.

[darylwright]

The following find and replace regex can be used (in WebStorm at least) to quickly convert the existing lexer test data to test declarations referencing a 'macro' function:

Find: \{\n\s+pattern:\s+('[^\n]+'|`[\w\s.;\\]*`),\n\s+expected:\s+(\[([\s\w{}',:$.]*)\]),\n\s+title:\s+('[^\n]+')\n\s+}
Replace: test($4, macro, $1, $2);

Some minor clean up will be necessary afterwards.

Edit: The regex may need to be updated as necessary.

[darylwright]

🎉 This issue has been resolved in version 2.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀