Vignesh.. Thanks for this post. Once code is released the issue of backwards compatibility is a major concern. I think your team did the right thing. Now that its a known potential bug. It can be worked on later. It does however underscore the importance of regression testing.
I've recently converted to Cypress for regression testing. It makes me feel safe..
Thanks for the suggestion John, I checked Cypress before and couldn't use it because it was not supported by browserstack. We are using browserstack to run E2E tests using protractor before deploying to staging. The main issue here is, Our app is constantly evolving and it is really hard to keep the tests in the same pace. we are trying to do that and improve coverage.
No, I heard about them when reading about selenium, but I am not sure of them in Angular and protractor's context. But when I think about it for E2E tests, it shouldn't matter if I use angular or just Vanilla JS. So I will look into it and see if I can bring them into our tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Vignesh.. Thanks for this post. Once code is released the issue of backwards compatibility is a major concern. I think your team did the right thing. Now that its a known potential bug. It can be worked on later. It does however underscore the importance of regression testing.
I've recently converted to Cypress for regression testing. It makes me feel safe..
Good luck...
Thanks for the suggestion John, I checked Cypress before and couldn't use it because it was not supported by browserstack. We are using browserstack to run E2E tests using protractor before deploying to staging. The main issue here is, Our app is constantly evolving and it is really hard to keep the tests in the same pace. we are trying to do that and improve coverage.
Yes understood. Are you using page object models? And can you auto create them?
No, I heard about them when reading about selenium, but I am not sure of them in Angular and protractor's context. But when I think about it for E2E tests, it shouldn't matter if I use angular or just Vanilla JS. So I will look into it and see if I can bring them into our tests.