Rspec group test ouput
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
0
How group some tests to be displayed in a group ?
I launch :
bin/rspec --format=documentation
Actual, I got :
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
And I want to have :
API
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
Repository
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
The tests that's concern API, are grouped togheter.
The tests that's concern Repository, are grouped togheter.
I want this to better organize the visualisation and exploration of my tests
EDIT :
context (see mrzasa response) do not fill my requirements :
Repository
AddressRepository
#create
create address in database
Repository
AgencyRepository
#create
create agency in database
Repository
ArticleRepository
#create
create article in database
ruby-on-rails ruby rspec rspec-rails
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
add a comment |
0
How group some tests to be displayed in a group ?
I launch :
bin/rspec --format=documentation
Actual, I got :
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
And I want to have :
API
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
Repository
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
The tests that's concern API, are grouped togheter.
The tests that's concern Repository, are grouped togheter.
I want this to better organize the visualisation and exploration of my tests
EDIT :
context (see mrzasa response) do not fill my requirements :
Repository
AddressRepository
#create
create address in database
Repository
AgencyRepository
#create
create agency in database
Repository
ArticleRepository
#create
create article in database
ruby-on-rails ruby rspec rspec-rails
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
add a comment |
0
0
0
How group some tests to be displayed in a group ?
I launch :
bin/rspec --format=documentation
Actual, I got :
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
And I want to have :
API
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
Repository
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
The tests that's concern API, are grouped togheter.
The tests that's concern Repository, are grouped togheter.
I want this to better organize the visualisation and exploration of my tests
EDIT :
context (see mrzasa response) do not fill my requirements :
Repository
AddressRepository
#create
create address in database
Repository
AgencyRepository
#create
create agency in database
Repository
ArticleRepository
#create
create article in database
ruby-on-rails ruby rspec rspec-rails
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
How group some tests to be displayed in a group ?
I launch :
bin/rspec --format=documentation
Actual, I got :
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
And I want to have :
API
Countries API
GET /countries
return list of countries
returns status code 200
GET /states/{country_abbrev}
return list of states
returns status code 200
Companies API
GET /companies
returns companies
returns status code 200
Repository
InvoiceLineRepository
#create
create invoice line in database
InvoiceRepository
#create
create invoice in database
The tests that's concern API, are grouped togheter.
The tests that's concern Repository, are grouped togheter.
I want this to better organize the visualisation and exploration of my tests
EDIT :
context (see mrzasa response) do not fill my requirements :
Repository
AddressRepository
#create
create address in database
Repository
AgencyRepository
#create
create agency in database
Repository
ArticleRepository
#create
create article in database
ruby-on-rails ruby rspec rspec-rails
ruby-on-rails ruby rspec rspec-rails
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
edited Nov 22 '18 at 10:49
Xero
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
asked Nov 22 '18 at 10:24
XeroXero
1,72321846
1,72321846
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
1
You could implement a custom formatter, take a look at the documentation formatter for an example, but as others have said this does not scale, and what exactly is a "group"?
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
add a comment |
0
You need to add contexts for API and Repository:
context 'API' do
context 'Countries' do
describe 'GET /countries' do
# examples
end
describe 'GET /states/{country_abbrev}' do
# examples
end
end
end
context 'Repository do
# context/describe blocks for InvoiceLineRepository and InvoiceRepository
end
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
2
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428785%2frspec-group-test-ouput%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
You could implement a custom formatter, take a look at the documentation formatter for an example, but as others have said this does not scale, and what exactly is a "group"?
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
add a comment |
1
You could implement a custom formatter, take a look at the documentation formatter for an example, but as others have said this does not scale, and what exactly is a "group"?
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
add a comment |
1
1
1
You could implement a custom formatter, take a look at the documentation formatter for an example, but as others have said this does not scale, and what exactly is a "group"?
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
You could implement a custom formatter, take a look at the documentation formatter for an example, but as others have said this does not scale, and what exactly is a "group"?
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
answered Nov 22 '18 at 11:26
Mihai TârnovanMihai Târnovan
513512
513512
add a comment |
add a comment |
0
You need to add contexts for API and Repository:
context 'API' do
context 'Countries' do
describe 'GET /countries' do
# examples
end
describe 'GET /states/{country_abbrev}' do
# examples
end
end
end
context 'Repository do
# context/describe blocks for InvoiceLineRepository and InvoiceRepository
end
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
2
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
add a comment |
0
You need to add contexts for API and Repository:
context 'API' do
context 'Countries' do
describe 'GET /countries' do
# examples
end
describe 'GET /states/{country_abbrev}' do
# examples
end
end
end
context 'Repository do
# context/describe blocks for InvoiceLineRepository and InvoiceRepository
end
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
2
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
add a comment |
0
0
0
You need to add contexts for API and Repository:
context 'API' do
context 'Countries' do
describe 'GET /countries' do
# examples
end
describe 'GET /states/{country_abbrev}' do
# examples
end
end
end
context 'Repository do
# context/describe blocks for InvoiceLineRepository and InvoiceRepository
end
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
You need to add contexts for API and Repository:
context 'API' do
context 'Countries' do
describe 'GET /countries' do
# examples
end
describe 'GET /states/{country_abbrev}' do
# examples
end
end
end
context 'Repository do
# context/describe blocks for InvoiceLineRepository and InvoiceRepository
end
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
answered Nov 22 '18 at 10:40
mrzasamrzasa
10.7k104079
10.7k104079
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
2
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
add a comment |
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
2
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
I updated my answer, context do not fill my requirements =/
– Xero
Nov 22 '18 at 10:49
2
2
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
...But it's worth pointing out that this idea does not scale. It may look pretty for tiny output like OP's, but if you have 100s of endpoints then this file will quickly grow out of control and become difficult to maintain.
– Tom Lord
Nov 22 '18 at 11:07
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428785%2frspec-group-test-ouput%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
