INRIA/spoon

Improve tests in Spoon

Open

#1,818 opened on Jan 12, 2018

View on GitHubContributor guide
 (8 comments) (0 reactions) (0 assignees)Java (383 forks)github user discovery
good first issuehelp wantedtest

Repository metrics

Stars
 (1,933 stars)
PR merge metrics
 (Avg merge 19d 11h) (49 merged PRs in 30d)

Description

I just had a report from @oscarlvp who is working on software testing that we have a lot of methods not properly tested in Spoon. For a lot of them we have a coverage, but removing the body of the method does not change at all the test results. For other methods, deciding an arbitrary return value (like return true) does not change either the test results.

So we should improve our test basis. The complete list of badly tested methods (and why) is available there: https://github.com/STAMP-project/descartes-experiments/blob/master/spoon/index.md

Contributor guide

Research direction
For each method listed in the provided link, examine the existing test and add assertions that verify the method's behavior. Ensure the test fails if the method body is removed or returns a dummy value.
Tech stack
java
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Javatesting concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55