guide-for-testing

[CLAassistant]

All committers have signed the CLA.

[GuentherJulian]

You simply link the Quarkus guide in your guide, which is fine in many cases. But we also need to see if there are any differences with the existing Testing Guide from devon4j. For example, the existing guide for Spring applications says to use AssertJ as the assertion framework. The Quarkus guide depends on REST Assured, if I understand correctly. So the existing guide is not a general guide for Spring and Quarkus, if we say in another guide that the user must use a different framework in Quarkus. Either we need to remove those parts of the general guide and create different guides for Spring and Quarkus. Or we need to check if it is possible to use AssertJ in Quarkus as well. But then we can't just refer to the original Quarkus guide. In any case we need to link your guide in the general guide so that user can easily jump to your guide when they read something about testing in the general guide.

[lilliCao]

Review and Changes:

• keep the following sections in the general guides with minor changes
  • General best practices
  • Test automation
  • Test Doubles
  • Integration levels
  • Regression testing
  • Deployment Pipeline
  • Test Coverage
  • Debugging tests
• Move Spring-Test implementation and Spring-Test configuration to spring-testing-guide
• Add Quarkus test configuration in quarkus-testing-guide

@GuentherJulian

[maybeec]

closes devonfw/devon4quarkus#11