Terminology: Logical/Concrete Test Case
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation, testing
Research direction
Start by reading chapter "3. Terminology" in the spec and the discussion referenced in issue #66. Review every use of "logical test case" and "logical run", then update the terminology and Test Case definition so the proposed distinction is consistent throughout the spec.
Written by the indexing model from the issue text.
Description
I'd like to shed light on the term "logical test case".
Preface: Currently the spec in chapter "3. Terminology" does not "define" the term "logical test case".
Problem
IMHO, the term “logical test case” causes confusion when used in conjunction with the parameterization of test cases because it refers to something "abstract". But the opposite is the case.
Why?
- A test case consists of a flow logic plus a set of parameters.
- In case of an non-empty set of parameters the same flow logic is executed multiple times.
- So it can be said that the flow logic is not "complete" and not "concrete" enough.
- So it could also be said that the flow logic actually is the "logical" part of each of the concrete executions.
Proposal
I propose to:
- exchange "logical test case" by "concrete test case" in the spec
- extend the definition of "Test Case" as followed:
Test Case:
An individual executable test, represented in CTRF as an entry within the tests array.
An individual executable test, if parametrized, consists of the flow logic and a set of parameters.
This combination forms a "Concrete Test Case".
This is not yet streamlined, you will probably come up with a better way to phrase it.
Notes:
- By the way , this is not contradictory to "logical run". A "logical run" consists of multiple "concrete runs".
- I felt obliged to mention the term “concrete test case” in my comment to issue #66 because I suspect that the term “logical test case” obscures our understanding of
testId.
- Dominant language
- No language data
- Stars
- 98
- Forks
- 4
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from ctrf-io/ctrf
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
yetone/magpie#1032 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MicrosoftLearning/PL-400_Microsoft-Power-Platform-Developer#231 ·
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
VenetoStato/giorgio#6 ·
-
specification
Difficulty 1/5 Under an hour Newbie friendliness 85/100
WICG/webmonetization#754 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linagora/twake-on-matrix#3446 ·
Maintainers usually reply within 3 days