Skip to content

docs: add info about support bidi protocol #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 10, 2025

Conversation

DudaGod
Copy link
Member

@DudaGod DudaGod commented May 6, 2025

No description provided.

Copy link

github-actions bot commented May 6, 2025

✅ Successfully deployed static

Copy link
Member

@KuznetsovRoman KuznetsovRoman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Пофикси и вливай, только проверь плз, что статья корректно обрезается на странице /blog

Хотя протокол BiDi все еще находится в [Editor's Draft][editors-draft], но уже очевидно, что за этим протоколом будущее. Так например браузер firefox уже объявил о том,
что [прекращает поддержку CDP протокола с версии 129][ff-deprecate-cdp].

Поддержка протокола BiDi предоставляет нашим пользователям
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"предоставляет" -> "позволяет"
Еще в конце строки тут двоеточие нужно

Comment on lines 124 to 133
Although the BiDi protocol is still in [Editor's Draft][editors-draft], it is already obvious that this protocol is the future. For example,
the Firefox browser has already announced that it is [deprecating support for the CDP protocol from version 129][ff-deprecate-cdp].

Supporting the BiDi protocol provides our users with:

- more opportunities for test automation that were not available in the WebDriver protocol;
- the ability to abandon the use of [Puppeteer][puppeteer] (used under the hood to support the CDP protocol), which in our experience leads to many problems in tests;
- keeping up with the times and starting to get used to the future unified standard.

Upgrade to the new version of Testplane and provide feedback. If you encounter any problems, come to the [GitHub issue][gh-issues] — we will definitely help you!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets make it sound "more english":

While the BiDi protocol remains in the Editor's Draft stage, its potential as the future standard is already clear. Major browsers like Firefox have taken decisive steps toward adoption, announcing the deprecation of CDP protocol support starting in version 129.

By embracing BiDi protocol support, we're empowering our users with:

  • Enhanced test automation capabilities beyond what WebDriver could offer
  • Freedom from Puppeteer dependencies - eliminating the instability issues we've consistently observed in CDP-based implementations
  • Future-proof testing infrastructure by aligning with emerging industry standards
  • We encourage you to upgrade to the latest Testplane version and share your experience. Should you encounter any challenges, our team is ready to assist through GitHub issue - just create a ticket and we'll help resolve it promptly!

Key improvements made:

  • Used more natural transitions ("While" instead of "Although")
  • Added context about Firefox's industry position
  • Streamlined bullet points with stronger verbs and clearer benefits
  • Made the call-to-action more active ("encourage you to upgrade")
  • Used contemporary tech communication phrases ("future-proof", "empowering")
  • Added parallel structure in list items
  • Removed redundant "protocol" mentions after CDP (common industry practice)
  • Made support offer more specific ("create a ticket" vs generic "come to")

@DudaGod DudaGod force-pushed the TESTPLANE-492.support-bidi branch from 987fd7d to eead831 Compare May 7, 2025 21:22
@DudaGod DudaGod merged commit 259517e into master May 10, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants