Protractor not getting elements












0














I've got an Angular 6 app with e2e test I'm trying to make. In this test I first login, then trying to get all menu items and click over them, however I'm unable even to get a menu. My test results in timeout




should easily navigate by menu
- Failed: script timeout: result was not received in 11 seconds
(Session info: chrome=70.0.3538.77)




And first string from below (any way it doesn't make much sense)




From: Task: Protractor.waitForAngular() - Locator: [object Object]
at Driver.schedule




describe('Walking through', () => {

let page: AppPage;

beforeEach(() => {
page = new AppPage();
});

it('should be at proper url', () => {
page.navigateTo();
page.logIn(
'test',
'password'
);
expect(
browser.wait(browser.ExpectedConditions.urlContains('dashboard'), 5000)
.catch(() => false)
).toBeTruthy();
});

// Not working
it('should easily navigate by menu', () => {
const menu = element(by.css('.menu'));

expect(menu).toBeTruthy();

const menuItems = element(menu).all(by.tagName('li'));

expect(menuItems).toBeTruthy();

menuItems.each(e => {
browser.sleep(500);
e.click();
expect(e).toBeTruthy();
});
});
});









share|improve this question






















  • You don't navigate to your page in the second test, and you don't login.
    – JB Nizet
    Nov 23 '18 at 8:29










  • Of course, because I've done it before. It works continuously not running it from scratch if I don't specify so. Moreover, I've been observing the tests and it was staying right on the page it had to found an element.
    – Sergey
    Nov 23 '18 at 9:19










  • Tests are supposed to be independent of each other. And BTW jasmine now runs them in a random order, on purpose.
    – JB Nizet
    Nov 23 '18 at 9:21










  • It's a protractor which runs them by ORDER. Check it yourself. There is no logic in things you say in way of testing business logic. I may need to log in once, than a thousand times just for each test.
    – Sergey
    Nov 23 '18 at 9:42










  • protractortest.org/#/…
    – JB Nizet
    Nov 23 '18 at 9:48
















0














I've got an Angular 6 app with e2e test I'm trying to make. In this test I first login, then trying to get all menu items and click over them, however I'm unable even to get a menu. My test results in timeout




should easily navigate by menu
- Failed: script timeout: result was not received in 11 seconds
(Session info: chrome=70.0.3538.77)




And first string from below (any way it doesn't make much sense)




From: Task: Protractor.waitForAngular() - Locator: [object Object]
at Driver.schedule




describe('Walking through', () => {

let page: AppPage;

beforeEach(() => {
page = new AppPage();
});

it('should be at proper url', () => {
page.navigateTo();
page.logIn(
'test',
'password'
);
expect(
browser.wait(browser.ExpectedConditions.urlContains('dashboard'), 5000)
.catch(() => false)
).toBeTruthy();
});

// Not working
it('should easily navigate by menu', () => {
const menu = element(by.css('.menu'));

expect(menu).toBeTruthy();

const menuItems = element(menu).all(by.tagName('li'));

expect(menuItems).toBeTruthy();

menuItems.each(e => {
browser.sleep(500);
e.click();
expect(e).toBeTruthy();
});
});
});









share|improve this question






















  • You don't navigate to your page in the second test, and you don't login.
    – JB Nizet
    Nov 23 '18 at 8:29










  • Of course, because I've done it before. It works continuously not running it from scratch if I don't specify so. Moreover, I've been observing the tests and it was staying right on the page it had to found an element.
    – Sergey
    Nov 23 '18 at 9:19










  • Tests are supposed to be independent of each other. And BTW jasmine now runs them in a random order, on purpose.
    – JB Nizet
    Nov 23 '18 at 9:21










  • It's a protractor which runs them by ORDER. Check it yourself. There is no logic in things you say in way of testing business logic. I may need to log in once, than a thousand times just for each test.
    – Sergey
    Nov 23 '18 at 9:42










  • protractortest.org/#/…
    – JB Nizet
    Nov 23 '18 at 9:48














0












0








0







I've got an Angular 6 app with e2e test I'm trying to make. In this test I first login, then trying to get all menu items and click over them, however I'm unable even to get a menu. My test results in timeout




should easily navigate by menu
- Failed: script timeout: result was not received in 11 seconds
(Session info: chrome=70.0.3538.77)




And first string from below (any way it doesn't make much sense)




From: Task: Protractor.waitForAngular() - Locator: [object Object]
at Driver.schedule




describe('Walking through', () => {

let page: AppPage;

beforeEach(() => {
page = new AppPage();
});

it('should be at proper url', () => {
page.navigateTo();
page.logIn(
'test',
'password'
);
expect(
browser.wait(browser.ExpectedConditions.urlContains('dashboard'), 5000)
.catch(() => false)
).toBeTruthy();
});

// Not working
it('should easily navigate by menu', () => {
const menu = element(by.css('.menu'));

expect(menu).toBeTruthy();

const menuItems = element(menu).all(by.tagName('li'));

expect(menuItems).toBeTruthy();

menuItems.each(e => {
browser.sleep(500);
e.click();
expect(e).toBeTruthy();
});
});
});









share|improve this question













I've got an Angular 6 app with e2e test I'm trying to make. In this test I first login, then trying to get all menu items and click over them, however I'm unable even to get a menu. My test results in timeout




should easily navigate by menu
- Failed: script timeout: result was not received in 11 seconds
(Session info: chrome=70.0.3538.77)




And first string from below (any way it doesn't make much sense)




From: Task: Protractor.waitForAngular() - Locator: [object Object]
at Driver.schedule




describe('Walking through', () => {

let page: AppPage;

beforeEach(() => {
page = new AppPage();
});

it('should be at proper url', () => {
page.navigateTo();
page.logIn(
'test',
'password'
);
expect(
browser.wait(browser.ExpectedConditions.urlContains('dashboard'), 5000)
.catch(() => false)
).toBeTruthy();
});

// Not working
it('should easily navigate by menu', () => {
const menu = element(by.css('.menu'));

expect(menu).toBeTruthy();

const menuItems = element(menu).all(by.tagName('li'));

expect(menuItems).toBeTruthy();

menuItems.each(e => {
browser.sleep(500);
e.click();
expect(e).toBeTruthy();
});
});
});






angular protractor angular-e2e






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 23 '18 at 8:25









Sergey

901317




901317












  • You don't navigate to your page in the second test, and you don't login.
    – JB Nizet
    Nov 23 '18 at 8:29










  • Of course, because I've done it before. It works continuously not running it from scratch if I don't specify so. Moreover, I've been observing the tests and it was staying right on the page it had to found an element.
    – Sergey
    Nov 23 '18 at 9:19










  • Tests are supposed to be independent of each other. And BTW jasmine now runs them in a random order, on purpose.
    – JB Nizet
    Nov 23 '18 at 9:21










  • It's a protractor which runs them by ORDER. Check it yourself. There is no logic in things you say in way of testing business logic. I may need to log in once, than a thousand times just for each test.
    – Sergey
    Nov 23 '18 at 9:42










  • protractortest.org/#/…
    – JB Nizet
    Nov 23 '18 at 9:48


















  • You don't navigate to your page in the second test, and you don't login.
    – JB Nizet
    Nov 23 '18 at 8:29










  • Of course, because I've done it before. It works continuously not running it from scratch if I don't specify so. Moreover, I've been observing the tests and it was staying right on the page it had to found an element.
    – Sergey
    Nov 23 '18 at 9:19










  • Tests are supposed to be independent of each other. And BTW jasmine now runs them in a random order, on purpose.
    – JB Nizet
    Nov 23 '18 at 9:21










  • It's a protractor which runs them by ORDER. Check it yourself. There is no logic in things you say in way of testing business logic. I may need to log in once, than a thousand times just for each test.
    – Sergey
    Nov 23 '18 at 9:42










  • protractortest.org/#/…
    – JB Nizet
    Nov 23 '18 at 9:48
















You don't navigate to your page in the second test, and you don't login.
– JB Nizet
Nov 23 '18 at 8:29




You don't navigate to your page in the second test, and you don't login.
– JB Nizet
Nov 23 '18 at 8:29












Of course, because I've done it before. It works continuously not running it from scratch if I don't specify so. Moreover, I've been observing the tests and it was staying right on the page it had to found an element.
– Sergey
Nov 23 '18 at 9:19




Of course, because I've done it before. It works continuously not running it from scratch if I don't specify so. Moreover, I've been observing the tests and it was staying right on the page it had to found an element.
– Sergey
Nov 23 '18 at 9:19












Tests are supposed to be independent of each other. And BTW jasmine now runs them in a random order, on purpose.
– JB Nizet
Nov 23 '18 at 9:21




Tests are supposed to be independent of each other. And BTW jasmine now runs them in a random order, on purpose.
– JB Nizet
Nov 23 '18 at 9:21












It's a protractor which runs them by ORDER. Check it yourself. There is no logic in things you say in way of testing business logic. I may need to log in once, than a thousand times just for each test.
– Sergey
Nov 23 '18 at 9:42




It's a protractor which runs them by ORDER. Check it yourself. There is no logic in things you say in way of testing business logic. I may need to log in once, than a thousand times just for each test.
– Sergey
Nov 23 '18 at 9:42












protractortest.org/#/…
– JB Nizet
Nov 23 '18 at 9:48




protractortest.org/#/…
– JB Nizet
Nov 23 '18 at 9:48












0






active

oldest

votes











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


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53442981%2fprotractor-not-getting-elements%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53442981%2fprotractor-not-getting-elements%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

What visual should I use to simply compare current year value vs last year in Power BI desktop

Alexandru Averescu

Trompette piccolo