-
Notifications
You must be signed in to change notification settings - Fork 341
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
[Specs] Adopt subject convention #92
Comments
What is ‘sut’ ? Do you mean ‘subject’ ? |
System Under Test I learned in a screencast of qualitycoding.org and immediately fell in love with the concept. Around CP it is already used but not consistently in all the specs. |
I hate acronyms. Exactly because it means that others won’t know what it means, like I did :) Can we use the unambiguous term ‘subject’ please? (It’s used in other testing frameworks and stems from Test Subject in e.g. clinical trials.) |
|
Yeah I agree, that’s a good thing. |
Closing because it looks like that |
In fact, it’s outright hate! 😈 |
lol |
The system under test should be referenced by the
sut
acronym instead of using different names. This convention is concise and simplifies refactors.For example
@set
should be changed to@sut
in this lineThe text was updated successfully, but these errors were encountered: