eventsourcing/es4j

Problem: writing test suites for es4j apps is difficult

Open

#122 opened on Jul 10, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (27 forks)batch import
help wanted

Repository metrics

Stars
 (406 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Writing tests for es4j-powered apps is always a little bit of a hassle. To list a few issues:

  • making sure every test gets the proper clean slate setup
  • reducing the setup time
  • making it compact and DRY
  • (for some apps) a need to test against different journal and index engine backends.

Proposed solution: implement an eventsourcing-test module that will cover this.

Contributor guide

Research direction
Examine the current es4j framework's testing patterns and design a reusable test module for event sourcing applications.
Tech stack
java
Domain
backend
Issue type
Feature
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60