getappmap / getappmap/appmap-js

Gradle-based test execution produced zero appmaps

Open
#660 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
53
Forks
18
Avg merge
3d 18h
Merged PRs (30d)
8

Description

I clonsed https://github.com/spring-projects/spring-petclinic and executed the wizard to create tests for gradle test.

The final screen told me that 0 appmaps were created.
Maven-based test execution in the same repo produced 40 appmaps.


   ╭───────────────────────────────────────────────────────────────────────────────────────╮
   │                                                                                       │
   │                Success! There are now 0 AppMap files in directory '.'.                │
   │                                                                                       │
   │                                NEXT STEP: Open AppMaps                                │
   │                                                                                       │
   │   Return to the AppMap extension in your code editor to open and view your AppMaps.   │
   │                                                                                       │
   ╰───────────────────────────────────────────────────────────────────────────────────────╯

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report in spring-petclinic by running the wizard for gradle test, then compare its result with the Maven-based execution that creates 40 AppMaps. Trace the Gradle test-execution entry point and determine why it reports zero files; done means the Gradle workflow creates AppMaps rather than displaying zero.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, testing-qa, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.