Better unit test output

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
compilers, testing-qa

Research direction

Start by reviewing the JUnit test output produced by Less-Java and the generated-source reference described in issue #11. The work is done when test failures report objects and line numbers mapped back to the Less-Java source, using either a custom harness or parsed output.

Written by the indexing model from the issue text.

Description

enhancement

Less-Java emits JUnit test cases.

The test output comes from JUnit and may refer to objects and line numbers in the generated java source as described in #11.

Solutions:

  • Implement a custom testing harness from the ground up
  • Parse the output and map the references back to the less-java source
Dominant language
Java
Stars
6
Forks
7
No merged PRs in 30d

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.

More from JMU-CS/less-java

All issues in JMU-CS/less-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.