Developer can manually add or replace parser in parser resource

[tukanos]

Allow in testing manually replace parser that is automatically created.

[kursjan]

Can you add a comment why you need this? What is the use case for this behavior?

[tukanos]

@kursjan certainly. My use-case is to test all parser combinations, which can be created. For example, with different thousand, decimal separators or with different kinds of brackets/braces that could come in the future.

I could circumvent it by using multiple test classes where I would create the combinations. This patch allows you to test a a parser, toss it away. Have then a new parser with different setup and use tests created for that parser. All tested at one iteration.

I could create all parsers at once and store them at resource. In this instance, I don't want that because I want to test the one parser only and not other combination(s). The parsers are also created by default by using their #parserName with default values that I don't want. I want to have parser defined by me and that should be used for testing.