5.4.3 Release Without Release Notes or Changelog #5390
Comments
|
In related news, the Angular 9 RC11 from last night updates protractor from 5.4.2 to 5.4.3: https://github.com/angular/angular-cli/releases/tag/v9.0.0-rc.11 |
|
Slowly? Several years without any steps it's not slowly. |
|
It's far from being abandoned in terms of use. A lot of people still rely on it, me included. |
|
The changes from 5.4.2 to 5.4.3 are few as visible in the diff: https://github.com/angular/protractor/compare/5.4.2..5.4.3 Basically:
|
|
@AugustusKling Thanks for posting that. This project as far as I know is not abandoned (quick or slow). Is it dead? Not that I am aware of. I am working on a different team (not Protractor) that uses Protractor as a dependency. We still rely on it too. Moving forward the continued support will be provided by the Angular team. Happy testing everyone! |
|
Can we expect Protractor 6 anytime soon? |
|
@Phonesis That's a good question for the Angular team. Most of the work we did last year was to move off of the control flow and deprecate old promise libraries. There are a few outstanding issues (as far as I know of):
Why did we decide to not do a 6 release last year? We pulled back the release initially because it was not documented for users still on the control flow. I think there still needs some documentation around this as well as a control flow migration story. (Also I updated this comment because I was using a different ortho keyboard and I thought I was hitting the backspace button but published my WIP comment and closed the issue) |
|
Sorry about that - I did update the changelog, but forgot to merge it: https://github.com/angular/protractor/blob/release-5.4/CHANGELOG.md This was a small release to fix an issue that was preventing Angular from updating to TypeScript 3.7. Protractor 5 is the last version of Protractor that uses the deprecated WebDriver control flow (see SeleniumHQ/selenium#2969). Future updates to Protractor 5 will be on the 'release-5.4' branch. We don't want to break people with updates to Protractor 5, so we won't be updating the version of WebDriver it uses. Unfortunately, the latest version of Chrome uses the W3C standard actions API, which is not compatible with the version of WebDriver that we've pinned Protractor 5 to. This means that Chrome v74 is the last version of Chrome that fully works with Protractor 5. Future versions of Chrome still mostly work, just not low-level mouse control via the Actions API. That's why I updated our CI to use Chrome v74. The master branch is Protractor 6. Unfortunately, Protractor 6 is a major breaking change. With the WebDriver control flow deprecated, tests need to be rewritten to use We don't want to actually release Protractor 6 until we have some documentation and tooling to help people migrate off the control flow. However, if you'd like to get a head start, you can disable the control flow on Protractor 5 (see https://github.com/angular/protractor/blob/release-5.4/docs/control-flow.md). Once your tests pass with the control flow disabled, you should be able to update to Protractor 6. |
|
You mention we can move to Protractor 6 if our tests pass the control flow.
6.0 current has a number of issues, for example when i goto run a test I
get the following error: protractor Key:
import("./selenium-webdriver/lib/input").IKey;
There are a few open defects about this. Are 6.0 issues going to be
addressed?
…On Wed, Feb 5, 2020 at 6:47 PM Michael Giambalvo ***@***.***> wrote:
Sorry about that - I did update the changelog, but forgot to merge it:
https://github.com/angular/protractor/blob/release-5.4/CHANGELOG.md
This was a small release to fix an issue that was preventing Angular from
updating to TypeScript 3.7. Protractor 5 is the last version of Protractor
that uses the deprecated WebDriver control flow (see
SeleniumHQ/selenium#2969
<SeleniumHQ/selenium#2969>). Future updates to
Protractor 5 will be on the 'release-5.4' branch. We don't want to break
people with updates to Protractor 5, so we won't be updating the version of
WebDriver it uses. Unfortunately, the latest version of Chrome uses the W3C
standard actions API, which is not compatible with the version of WebDriver
that we've pinned Protractor 5 to. This means that Chrome v74 is the last
version of Chrome that fully works with Protractor 5. Future versions of
Chrome still mostly work, just not low-level mouse control via the Actions
API. That's why I updated our CI to use Chrome v74.
The master branch is Protractor 6. Unfortunately, Protractor 6 is a major
breaking change. With the WebDriver control flow deprecated, tests need to
be rewritten to use async/await rather than rely on the process manager.
We did this in Google a couple years ago.
We don't want to actually release Protractor 6 until we have some
documentation and tooling to help people migrate off the control flow.
However, if you'd like to get a head start, you can disable the control
flow on Protractor 5 (see
https://github.com/angular/protractor/blob/release-5.4/docs/control-flow.md).
Once your tests pass with the control flow disabled, you should be able to
update to Protractor 6.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5390?email_source=notifications&email_token=AIJJ6SH6NG7TGZMYDRTGO5DRBNFXZA5CNFSM4KMXWOC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK5M3JI#issuecomment-582667685>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJJ6SGMRKLU6DDDRPKDHN3RBNFXZANCNFSM4KMXWOCQ>
.
|
|
@tfaron as far I know protractor 6.0 was retracted shortly after it was released. The current version available for protractor 6 has not been updated in 10 months and is not very unusable, again, as far as I know. I assume @heathkit was referring to update once it is officially released again in the near future. |
|
Michael Giambalvo mentioned the following so this is where some confusion
lies.
We don't want to actually release Protractor 6 until we have some
documentation and tooling to help people migrate off the control flow.
However, if you'd like to get a head start, you can disable the control
flow on Protractor 5 (see
https://github.com/angular/protractor/blob/release-5.4/docs/control-flow.md).
Once your tests pass with the control flow disabled, you should be able to
update to Protractor 6.
…On Thu, Feb 6, 2020 at 1:32 PM Lyubomir Aleksiev ***@***.***> wrote:
@tfaron <https://github.com/tfaron> as far I know protractor 6.0 was
retracted shortly after it was released. The current version available for
protractor 6 has not been updated in 10 months and is not very unusable,
again, as far as I know. I assume @heathkit <https://github.com/heathkit>
was referring to update once it is officially released again in the near
future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5390?email_source=notifications&email_token=AIJJ6SBJUMWVK7BQES2IYRDRBRJUNA5CNFSM4KMXWOC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELAJI3Q#issuecomment-583046254>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJJ6SGJMU3VKN23Y3SUAT3RBRJUNANCNFSM4KMXWOCQ>
.
|
|
It is wonderful to see an official-is declaration that the future is to move away from the old control flow and use async-await. I feel validated - we’ve already been teaching it that way for a while. |
|
Absolutely! Everyone should move off the control flow as soon as is convenient. @kylecordes Do you have any tools or documentation that might help people migrate? We thought this was more urgent last year, since Selenium 4 doesn't support the control flow. However, now that WebDriver is a W3C standard, things seem to be changing much more slowly. I don't know when Selenium 4 is actually going to be released, but presumably when that happens people will need to migrate in a hurry. |
|
I referred few examples available under Protractor - Reference and able to successfully migrate my code to async-await http://www.protractortest.org/#/async-await |
|
@heathkit do you have any clear idea on when we can be expecting Protractor 6 to be released? There is the constant fear from a lot of people that support for Protractor might be completely dropped soon which will leave a lot of us stranded. |
|
I second the concern of @Fuun347 |
|
Can we have a clear answer from Protractor members, please ? |
|
Can we get a roadmap? |
This is what we have for now: https://angular.io/guide/roadmap#update-our-e2e-testing-strategy Under the "In Progress" part of the Roadmap
|
|
@Splaktar This info published in @angular website almost year. Maybe you have more info and can tease something? |
There should be some updates coming soon on this, but I can share that we do not have the resources to support two actively developed versions of Protractor. |
|
@Splaktar But even one version (current 7.0) not supported, not actively nor at all - no PR merging, no bug fixing, no answers from official @angular team (your answers as exception, thank you:-) )We hope that @angular team as new repo Protractor owner will come back to Protractor support and improvements. Waiting for good news and roadmap. Thanks!) |
|
People concerned about the state of Protractor - why not just move to another solution? We moved all our e2e testing from Protractor to Cypress a year ago exactly because of this. It was not a cheap process initially, but has saved us exponentially more time and resources in the long run. Honestly, I don't even see why the scope of Angular should include maintaining an entire e2e stack these days when there are dedicated solutions for that. Just provide bindings for Cypress and similar solutions and focus on developing Angular itself. |
|
@csvan We didn’t find Cypress as solution which could done our needs in testing. It okay for small projects IMO. Also, at the same time we didn’t find it stable and don’t know what will be with it and other similar framework in 2-3 years. Cypress could die as quickly as it appeared. Protractor as seleneium wrapper is from 2013 as I remember. If protractor will be deprected, we will migrate to native selenium since it supported, has a big community and became as standard according to w3c, what not say about non-selenium frameworks like cypress. |
|
Just to add to the conversation. I work for a large company and we use Protractor to drive thousands of end to end tests. Of course, we have considered alternatives (Cypress, Test Cafe, and most promisingly Playwright). Playwright is the only alternative that offers what we need. A free model (no hidden pay walls), ability to emulate different browsers (not just chromium), and easy to mix it in with Cucumber.js. The main draw to Protractor for us though is it works great with tabs/frames (we have 'legacy' pains to deal with) as it is driven by webdriver protocol. Also, it has a very nice parallel execution configuration for sharding capabilities etc. So we would ideally like to stick with it as long as it eventually receives Selenium 4 support. I personally don't see the point in maintaining two versions. Just focus on the async/await support and ditch control flow. |
|
Seems like Protractor is officially dead. |
Hi there!
I see a newly-released 5.4.3 version but there is no accompanying release note or changelog update. Also, the changelog on master still reflects the 6.0.0 version that was pulled back, IIRC.
Thanks for continuing your work in this repo!
The text was updated successfully, but these errors were encountered: