-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's create real Equivalence classes #197
Comments
I implemented Date |
@vbriabrin also taking a look at this. Open question: how would this support be leveraged from models? Leveraging macros is straightforward from a model like SCXML. Can flags/options be added to macros to support boundary values or other Equivalence Class-like features? Another use case is using DG to generate input data for DB schemas, so covering basic SQL data types with these features would be helpful. CC: @mpeter28 |
#247 covers "boundary value" generation from macros. To clarify some terms around this:
What is being requested here is support for auto-generated equivalence classes, such as what a tester would create when performing equivalence class partitioning (defining boundary values, positive cases, negative cases, etc. for each variable). We need to do some brainstorming about the right way to do this:
Please come back with thoughts, and maybe break into additional tickets. dg-commons may be the right place to implement some of this logic. |
Now we have 'Equivalence classes' more like canned macros.
We need real Equivalence classes.
For most common data type like:
All these classes need at least:
By level I mean testing level like: 'min', 'normal' and 'max'.
'Normal' will extend 'min'. 'Max' will extend 'normal'
The text was updated successfully, but these errors were encountered: