MarketSquare / MarketSquare/robotframework-reporty

Decide on Data Model

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

Nobody has claimed this yet.

Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Which tables and columns do we need to visualize our data?
Do we need one table or multiple tables?

- Test Status per case
- Test Name
- Test Status
- Elapsed Time
- Start Time
- End Time
- Tags
- Message (for error)
- Metadata (Run, Release, ..)

- Test Status Overview
- Passed, Failed, Skipped , .. per Test Run

- ❓Keyword Status
- Which Keyword Level ? Only first level or also Library KWs ?

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.

Research direction

Start by reviewing the proposed test status, run overview, and keyword status fields in the issue. Decide whether one or multiple tables best represent them, and document an agreed set of tables and columns that covers the listed data and metadata.

Written by the indexing model from the issue text.

Assessment

Domain
data, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.