Skip to content
This repository was archived by the owner on Jan 30, 2025. It is now read-only.

Commit edec12c

Browse files
committed
Make migration to async API a short-term goal
1 parent 539ca65 commit edec12c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

ROADMAP.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,13 +48,8 @@ These are goals achievable within 3-6 months, tentatively done by Q2 2023.
4848
*Definition of Done*<br>
4949
Load test executed in Cloud can use xk6-browser API by importing `k6/x/browser`.
5050

51-
Mid-term goals
52-
--------------
53-
54-
These are goals achievable within 6-12 months, tentatively done by mid 2023.
55-
5651
- **Transition our API to be async/`Promise` based.**<br>
57-
Currently (April 2022), most of our API is synchronous. This is due to the historical fact that k6 didn't support async behavior because of a missing per-VU event loop.
52+
At the moment, most of our API is synchronous. This is due to the historical fact that k6 didn't support async behavior because of a missing per-VU event loop.
5853
[This event loop is now available](https://github.com/grafana/k6/pull/2228).
5954
Async APIs are important for a browser-testing tool, since most browser behavior and [CDP](https://chromedevtools.github.io/devtools-protocol/) (the protocol we use to communicate with the browser) is event-based. We need to expose an async API to implement this missing functionality and reach feature parity with tools like Playwright or Puppeteer.
6055

@@ -65,7 +60,12 @@ These are goals achievable within 6-12 months, tentatively done by mid 2023.
6560
When most of the API can be used asynchronously.
6661

6762

68-
- **Beta availability of the extension in k6 Cloud for all users.**<br>
63+
Mid-term goals
64+
--------------
65+
66+
These are goals achievable within 6-12 months, tentatively done by mid 2023.
67+
68+
- **Global availability of the extension in k6 Cloud for all users.**<br>
6969

7070
*How will we achieve this?*<br>
7171
The deployment should be optimized and the extension thoroughly tested before making it available to all users. Frontend changes should be done at this point, and usage costs (CPU, RAM, storage) and pricing details should be determined, followed by public announcements of the availability. Features such as screen capture, video recording, downloading, and file uploading should be available.

0 commit comments

Comments
 (0)