anchor.diff:  === Naming Convention for files
   
   * `.tpl.qute` will be processed with Qute and can use data (`.tpl.qute` will be removed from the output file name).
  -* certain common files, such as `readme.md`, `src/test/resources/application.yml`, `src/main/resources/META-INF/resources/index.html` are generated from the collected fragments found in the selected codestarts for the project
  +* certain common files, such as `readme.md`, `src/main/resources/application.yml`, `src/main/resources/META-INF/resources/index.html` are generated from the collected fragments found in the selected codestarts for the project
   * other files are copied.
   
   [#qute-templates]
  
positive.code: [#index-html]
  === index.html and web extension codestarts
  
  
  Extension codestarts may provide a snippet for the generated index.html by adding this file:
  
  base/src/main/resources/META-INF/resources/index.entry.qute.html:
  
negative.code: [#integration-test]
  === Integration test
  
  An extension is available to help test extension codestarts `QuarkusCodestartTest`. It provides a way to test:
  
  - the generated project content (with immutable mocked data) using snapshot testing
  - the generated project build/run (with real data) with helpers to run the build
  
  NOTE: Before all the tests, the extension will generate Quarkus projects in the specified languages with the given codestart using mocked data and real data. You can find those generated projects in the `target/quarkus-codestart-test` directory. You can open the `real-data` ones in your IDE or play with them using the terminal. *The real data is the easiest way to iterate on your extension codestart development.*
  
  
  The extension provides helpers to test that the projects build `buildAllProjects` or just a specific language project `buildProject(Language language)`. It also provides helpers to test the content with <<snapshot-testing>>.
  