odoo / odoo/runbot

Endpoint to easily get the current filters configuration & shit

Open
#536 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

runbot
Dominant language
Python
Stars
159
Forks
156
Avg merge
1d 13h
Merged PRs (30d)
16

Description

Currently when running code locally it's non-trivial to get what tests to run and what tests to ignore (because they're known to fail).

Would be nice if the various bits of configuration (-i and --test-tags basically) were available from the runbot's branches directly on easy to find endpoints, such that we could curl the data from the runbot to more easily reproduce test issues locally.

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 locating the runbot branch handling and the configuration that supplies the -i and --test-tags options. Define an easy-to-find endpoint exposing those values for each branch, then verify that curling it provides enough information to reproduce the runbot test selection locally.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.