Implement "trial --random" in terms of "trial --order"
Open
Nobody has claimed this yet.
enhancement
new
priority-normal
trial
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@Julian reported |
|---|---|
| Trac ID | trac#6451 |
| Type | enhancement |
| Created | 2013-04-21 17:45:18Z |
The API for providing the seed (or arbitrary args to order, see #6450) needs a tiny bit of thought, but something like
trial --order random --order-args seed:1243
is probably reasonable.
Searchable metadata
trac-id__6451 6451
type__enhancement enhancement
reporter__Julian Julian
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__trial trial
keywords__
time__1366566318000000 1366566318000000
changetime__1367185575000000 1367185575000000
version__None None
owner__
cc__jml
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing trial --order implementation and the related API discussion in issue #6450. Determine how a random order and its seed should be represented through the order interface, then add coverage for trial --random and its seed behavior. Done means random ordering is implemented in terms of trial --order without a separate code path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100