Skip to content
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

Closed
fabiopelosin opened this issue Apr 3, 2014 · 8 comments
Closed

[Specs] Adopt subject convention #92

fabiopelosin opened this issue Apr 3, 2014 · 8 comments

Comments

@fabiopelosin
Copy link
Member

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 line

@alloy
Copy link
Member

alloy commented Apr 3, 2014

What is ‘sut’ ? Do you mean ‘subject’ ?

@fabiopelosin
Copy link
Member Author

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.

@alloy
Copy link
Member

alloy commented Apr 3, 2014

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.)

@fabiopelosin
Copy link
Member Author

subject is fine for me, I'm just looking to standardise tests so they can be moved easily when code is factored out.

@alloy
Copy link
Member

alloy commented Apr 3, 2014

Yeah I agree, that’s a good thing.

@fabiopelosin fabiopelosin changed the title [Specs] Adopt sut convention [Specs] Adopt subject convention Apr 4, 2014
@fabiopelosin
Copy link
Member Author

Closing because it looks like that sut/subject are not getting much love from the rest of the team.

@alloy
Copy link
Member

alloy commented Aug 21, 2014

In fact, it’s outright hate! 😈

@fabiopelosin
Copy link
Member Author

lol

Ashton-W pushed a commit to Ashton-W/Core that referenced this issue Nov 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants