test(compatibility-suite): Implement V3 scenarios

[tienvx]

• Add services
  • Body validation
    • BodyStorage
    • BodyValidator
  • Convert fixture file to generators
    • GeneratorParser
    • GeneratorConverter
  • Apply generators to http request
    • RequestGeneratorBuilder
    • ResponseGeneratorBuilder
  • Apply generators to message
    • MessageGeneratorBuilder
  • Starting a server to capture generated value
    • GeneratorServer
  • Writing message to json pact file
    • MessagePactWriter
• Implement v3 scenarios
  • http
    • consumer
    • provider
  • message
    • consumer
    • provider
  • generators
  • matching rules
• Register V3 suites to behat
• Add v3 job to Compatibility Suite workflow
• There are 2 failed scenarios in v3 suite. Waiting for these PRs:
  • chore: Add @w.i.p tag to Kafka scenario  pact-compatibility-suite#6
  • feat: Use content type matching rule for V3 message's binary body pact-compatibility-suite#5

[Lewiscowles1986]

Can you force the failing cases to skip or xfail for now?
Even filtering out by tag would help https://docs.behat.org/en/v2.5/guides/6.cli.html#gherkin-filters

[tienvx]

Updated using tag filtering

[tienvx]

Updated using tag filtering

nevermind, it doesn't work as expected, close for now while waiting for the solution

[tienvx]

Fixed. It's a bit complicated than I thought.

There is no way I can set this filter to v3_message_provider suite's config:

            filters:
                name: '/^((?!Kafka|binary body \(negative).)*$/'

The filters array is flipped, probably because of this code https://github.com/Behat/Behat/blob/master/src/Behat/Behat/Gherkin/ServiceContainer/GherkinExtension.php#L97.

There is another option is to use --name flag. But because of the way it work (scenarios are not filtered if feature is matched), I have to filter out the feature as well.

 --name '/^((?!Kafka|binary body \(negative|Message provider).)*$/'

[Lewiscowles1986]

Hard to argue with well-documented, working code. Hope the other PR's land safely