NG Test show names in console
It can be quite difficult to identify a failing test when there is a fairly generic error (yes source maps is false) and would help greatly if we could show the test name instead of "executed 27 of 172"
Something like "executed 27 (TextActivityService Test) of 172
I'm referring here to when all tests pass but the console is reporting errors.
Is this possible?
angular angular-cli karma-runner
asked Dec 31 '18 at 11:56
72GM72GM
7582820
add a comment |
It can be quite difficult to identify a failing test when there is a fairly generic error (yes source maps is false) and would help greatly if we could show the test name instead of "executed 27 of 172"
Something like "executed 27 (TextActivityService Test) of 172
I'm referring here to when all tests pass but the console is reporting errors.
Is this possible?
angular angular-cli karma-runner
asked Dec 31 '18 at 11:56
72GM72GM
7582820
don't you just love the people that downvote but aren't big enough to add a comment... this is a perfectly reasonable question and if you'd been in this situation you'd understand why
– 72GM
Jan 7 at 8:16
add a comment |
It can be quite difficult to identify a failing test when there is a fairly generic error (yes source maps is false) and would help greatly if we could show the test name instead of "executed 27 of 172"
Something like "executed 27 (TextActivityService Test) of 172
I'm referring here to when all tests pass but the console is reporting errors.
Is this possible?
angular angular-cli karma-runner
asked Dec 31 '18 at 11:56
72GM72GM
7582820
It can be quite difficult to identify a failing test when there is a fairly generic error (yes source maps is false) and would help greatly if we could show the test name instead of "executed 27 of 172"
Something like "executed 27 (TextActivityService Test) of 172
I'm referring here to when all tests pass but the console is reporting errors.
Is this possible?
angular angular-cli karma-runner
angular angular-cli karma-runner
asked Dec 31 '18 at 11:56
72GM72GM
7582820
asked Dec 31 '18 at 11:56
72GM72GM
7582820
edited Jan 2 at 15:46
72GM
asked Dec 31 '18 at 11:56
72GM72GM
7582820
asked Dec 31 '18 at 11:56
72GM72GM
7582820
asked Dec 31 '18 at 11:56
72GM72GM
7582820
7582820
don't you just love the people that downvote but aren't big enough to add a comment... this is a perfectly reasonable question and if you'd been in this situation you'd understand why
– 72GM
Jan 7 at 8:16
add a comment |
don't you just love the people that downvote but aren't big enough to add a comment... this is a perfectly reasonable question and if you'd been in this situation you'd understand why
– 72GM
Jan 7 at 8:16
don't you just love the people that downvote but aren't big enough to add a comment... this is a perfectly reasonable question and if you'd been in this situation you'd understand why
– 72GM
Jan 7 at 8:16
don't you just love the people that downvote but aren't big enough to add a comment... this is a perfectly reasonable question and if you'd been in this situation you'd understand why
– 72GM
Jan 7 at 8:16
add a comment |
1 Answer
1
active
oldest
votes
When some unit test fails, it shows describe and it message as test case name.
For example:
describe('TestComponent', () => {
it('should pass test', () => {
expect(false).toBeTruthy();
});
});
Then, the above failed unit test will be shown as TestComponent should pass test FAILEDExpected false to be truthy
in the console.
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
@72GM In that case it would be better for you to addconsole.log("TextActivityService Test")at the start of the unit test. Basically, put the test name in console log.
– Saddam Pojee
Jan 2 at 15:52
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
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
});
}
});
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%2f53987213%2fng-test-show-names-in-console%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When some unit test fails, it shows describe and it message as test case name.
For example:
describe('TestComponent', () => {
it('should pass test', () => {
expect(false).toBeTruthy();
});
});
Then, the above failed unit test will be shown as TestComponent should pass test FAILEDExpected false to be truthy
in the console.
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
@72GM In that case it would be better for you to addconsole.log("TextActivityService Test")at the start of the unit test. Basically, put the test name in console log.
– Saddam Pojee
Jan 2 at 15:52
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
add a comment |
When some unit test fails, it shows describe and it message as test case name.
For example:
describe('TestComponent', () => {
it('should pass test', () => {
expect(false).toBeTruthy();
});
});
Then, the above failed unit test will be shown as TestComponent should pass test FAILEDExpected false to be truthy
in the console.
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
@72GM In that case it would be better for you to addconsole.log("TextActivityService Test")at the start of the unit test. Basically, put the test name in console log.
– Saddam Pojee
Jan 2 at 15:52
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
add a comment |
When some unit test fails, it shows describe and it message as test case name.
For example:
describe('TestComponent', () => {
it('should pass test', () => {
expect(false).toBeTruthy();
});
});
Then, the above failed unit test will be shown as TestComponent should pass test FAILEDExpected false to be truthy
in the console.
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
When some unit test fails, it shows describe and it message as test case name.
For example:
describe('TestComponent', () => {
it('should pass test', () => {
expect(false).toBeTruthy();
});
});
Then, the above failed unit test will be shown as TestComponent should pass test FAILEDExpected false to be truthy
in the console.
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
answered Dec 31 '18 at 13:46
Saddam PojeeSaddam Pojee
74819
74819
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
@72GM In that case it would be better for you to addconsole.log("TextActivityService Test")at the start of the unit test. Basically, put the test name in console log.
– Saddam Pojee
Jan 2 at 15:52
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
add a comment |
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
@72GM In that case it would be better for you to addconsole.log("TextActivityService Test")at the start of the unit test. Basically, put the test name in console log.
– Saddam Pojee
Jan 2 at 15:52
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
i mean when the test passes but throws an error in the console
– 72GM
Jan 2 at 15:45
@72GM In that case it would be better for you to add
console.log("TextActivityService Test") at the start of the unit test. Basically, put the test name in console log.– Saddam Pojee
Jan 2 at 15:52
@72GM In that case it would be better for you to add
console.log("TextActivityService Test") at the start of the unit test. Basically, put the test name in console log.– Saddam Pojee
Jan 2 at 15:52
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
That's what I'm trying to avoid tbh
– 72GM
Jan 7 at 8:15
add a comment |
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.
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%2f53987213%2fng-test-show-names-in-console%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
don't you just love the people that downvote but aren't big enough to add a comment... this is a perfectly reasonable question and if you'd been in this situation you'd understand why
– 72GM
Jan 7 at 8:16