TLDR The Angular team plans to end development of Protractor at the end of 2022 (in conjunction with Angular v15). Why? Protractor was created in 2013 when WebDriver APIs were not yet a standard and end-to-end (e2e) tests were hard to write due to lack of support for async / await. To solve this problem, Protractor wraps selenium-webdriver and abstracted asynchronous operations from developers wit
I'm interested in formalizing the contract between Test262 and the implementors who maintain harnesses to execute it. For instance, implementors currently have to infer that: most tests rely on a file named harness/sta.js. some tests mutate global state so as to make realm sharing unacceptable test code must be evaluated in the global scope I expect we will see more benefit from a document like th
There were some notes, and plans about a 1.0 release. I want to use this issue for any discussion and plans around it and start a complete list of tasks to do before we can release. There is this google doc that was started by @vojtajina and there was #944, which I will close in favor of this issue. Below is an incomplete list of things that need doing in my opinion. Organizational Clean up issue
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
