eiffel-community/eiffel-intelligence

Create tests for untested methods

Open

#446 opened on Mar 3, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Java (78 forks)auto 404
good first issuetest

Repository metrics

Stars
 (12 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

There are two untested methods, getAggregatedObjectByTemplateName and processQueryAggregatedObject, in the EI class ProcessAggregatedObject.

Motivation

Recently a bug in these two methods caused an error while testing aggregated object functionality at the EI frontend. In order to avoid any unintentional changes/errors, in future, these methods must be provided with testing code.

Exemplification

Benefits

Benefits of code testing

Possible Drawbacks

NO

Contributor guide

Research direction
Write unit tests for the getAggregatedObjectByTemplateName and processQueryAggregatedObject methods in the ProcessAggregatedObject class.
Tech stack
java
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaJUnit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70