Utilize Gradle TestKit

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
groovy

Research direction

Start by reviewing the existing tests and test resources, then identify where Gradle TestKit and Liberty server processes are used. Determine which tests can share a process, replace messages.log validation with MBean checks, and define how failing test folders should be archived.

Written by the indexing model from the issue text.

Description

Consolidate tests and test resources. Could some reuse the same Liberty process? We run the Liberty server in order to test certain features, but probably not necessary. Do not validate stuff through messages.log - use mbean instead.

zip/save folder when a test has a problem?

Dominant language
Groovy
Stars
52
Forks
48
Avg merge
21h 22m
Merged PRs (30d)
2

Getting set up

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 OpenLiberty/ci.gradle

All issues in OpenLiberty/ci.gradle

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.