As project owner I want in-house apps depicted with a coporate website such that users identify this as a SeqAn application.

Open
#26 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cmake
Domain
design, testing

Research direction

The issue does not identify files, test entry points, or a concrete implementation scope. First reconcile the corporate-branding request with the unrelated CLI coverage text and clarify the expected change and acceptance test; define what done means before implementation begins.

Written by the indexing model from the issue text.

Description

@rrahn commented on Thu Mar 26 2020

Description

The coverage tests should cover if possible the CLI tests. How can this be done if the CLI tests are called via a system call?

Acceptance Criteria
  • test
Tasks
  • task
Definition of Done
  • Implementation and design approved
  • Unit tests pass
  • Test coverage = 100%
  • Microbenchmarks added and/or affected microbenchmarks < 5% performance drop
  • API documentation added
  • Tutorial/teaching material added
  • Test suite compiles in less than 30 seconds (on travis)
  • Changelog entry added
Dominant language
CMake
Stars
6
Forks
9
Avg merge
23h 34m
Merged PRs (30d)
3

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 seqan/app-template

All issues in seqan/app-template

Similar issues

More Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.