-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Release v0.57.0 #4511
base: master
Are you sure you want to change the base?
Release v0.57.0 #4511
Conversation
Do we need to report it like? Updated github.com/grafana/xk6-redis from 0.3.2 to 0.3.3
9b614b9
to
07b48dd
Compare
|
||
## Breaking changes | ||
|
||
- [#4161](https://github.com/grafana/k6/pull/4161) Drops `k6/experimental/browser`. If you are still using it, please follow the [instructions](https://grafana.com/docs/k6/latest/using-k6-browser/migrating-to-k6-v0-52/) to move to the not experimental module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [#4161](https://github.com/grafana/k6/pull/4161) Drops `k6/experimental/browser`. If you are still using it, please follow the [instructions](https://grafana.com/docs/k6/latest/using-k6-browser/migrating-to-k6-v0-52/) to move to the not experimental module. | |
- [#4161](https://github.com/grafana/k6/pull/4161) Drops `k6/experimental/browser`. If you are still using it, please follow the [instructions](https://grafana.com/docs/k6/latest/using-k6-browser/migrating-to-k6-v0-52/) to move to the graduated and stable `k6/browser` module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@codebien suggestion is great 👍 . Two small nits, I would also replace "you are" with "you're" and remove "please".
|
||
The k6 team has been developing a new official jslib dedicated to functional testing. While it is still under active development and will potentially see breaking changes, the set of APIs and behaviors it offers are meant to make their way into k6 eventually, and it is now available for early feedback. | ||
|
||
[k6-testing](https://github.com/grafana/k6-jslib-testing) is a k6 javascript library that offers a seamless way to write functional tests in k6, using a Playwright-compatible assertions API. It exposes an `expect` function, with which assertions can be performed using specific matchers that reflect the expectation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[k6-testing](https://github.com/grafana/k6-jslib-testing) is a k6 javascript library that offers a seamless way to write functional tests in k6, using a Playwright-compatible assertions API. It exposes an `expect` function, with which assertions can be performed using specific matchers that reflect the expectation. | |
[k6-testing](https://github.com/grafana/k6-jslib-testing) is a k6 JavaScript library that offers a seamless way to write functional tests in k6, using a Playwright-compatible assertions API. It exposes an `expect` function, with which assertions can be performed using specific matchers that reflect the expectation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"expectation" at the end seems a little bit odd to me. What if we replaced it with "expected results"?
release notes/v0.57.0.md
Outdated
## _Optional_ Roadmap | ||
|
||
_Discussion of future plans_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joanlopez it would be good to announce the end-of-test summary's changes.
Co-authored-by: Ivan <2103732+codebien@users.noreply.github.com>
Co-authored-by: Ivan <2103732+codebien@users.noreply.github.com>
|
||
## Breaking changes | ||
|
||
- [#4161](https://github.com/grafana/k6/pull/4161) Drops `k6/experimental/browser`. If you are still using it, please follow the [instructions](https://grafana.com/docs/k6/latest/using-k6-browser/migrating-to-k6-v0-52/) to move to the not experimental module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@codebien suggestion is great 👍 . Two small nits, I would also replace "you are" with "you're" and remove "please".
|
||
The k6 team has been developing a new official jslib dedicated to functional testing. While it is still under active development and will potentially see breaking changes, the set of APIs and behaviors it offers are meant to make their way into k6 eventually, and it is now available for early feedback. | ||
|
||
[k6-testing](https://github.com/grafana/k6-jslib-testing) is a k6 javascript library that offers a seamless way to write functional tests in k6, using a Playwright-compatible assertions API. It exposes an `expect` function, with which assertions can be performed using specific matchers that reflect the expectation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"expectation" at the end seems a little bit odd to me. What if we replaced it with "expected results"?
import { expect } from "https://jslib.k6.io/k6-testing/0.2.0/index.js"; | ||
``` | ||
|
||
Try it out and give us feedback or contribute to the project on the [k6-jslib-testing repository](https://github.com/grafana/k6-jslib-testing)! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a question for the team, do we want to include a mention of this new library in the jslib docs page, or do we want to wait for some user feedback/more development before doing so?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good, left a few minor comments.
Also, since we created a v1.0.0-rc1 milestone, should we somehow announce it un Roadmap section?
The k6 team has been developing a new official jslib dedicated to functional testing. While it is still under active development and will potentially see breaking changes, the set of APIs and behaviors it offers are meant to make their way into k6 eventually, and it is now available for early feedback. | ||
|
||
[k6-testing](https://github.com/grafana/k6-jslib-testing) is a k6 javascript library that offers a seamless way to write functional tests in k6, using a Playwright-compatible assertions API. It exposes an `expect` function, with which assertions can be performed using specific matchers that reflect the expectation. | ||
When assertions fail, the test will immediately fail with a clear error message, including the expected and actual values in a similar fashion to what users would observe when using Playwright assertions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel that it's worth mentioning something like
When assertions fail, the test will immediately fail with a clear error message, including the expected and actual values in a similar fashion to what users would observe when using Playwright assertions. | |
Unlike current k6's `check` when `expects` assertions fail, the test will immediately fail with a clear error message, including the expected and actual values in a similar fashion to what users would observe when using Playwright assertions. |
Also, it could be something relevant to mention on https://grafana.com/docs/k6/latest/javascript-api/k6/check/
``` | ||
|
||
See the [csv module's documentation](https://grafana.com/docs/k6/latest/javascript-api/k6-experimental/csv/) for more information. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like a header here is missing, or at least we need a separator between the CSV new feature and the list.
Co-authored-by: Heitor Tashiro Sergent <heitortsergent@gmail.com> Co-authored-by: Oleg Bespalov <oleg.bespalov@grafana.com>
Reminder: We should also add recent k6-browser-related PRs to the release notes (e.g., #4531). @grafana/k6-core |
What?
This PR contains the Release notes for the upcoming k6 version v0.57.0. Please add commits as you see fit to update the content according to the changes you've made this cycle 🙇🏻
Related PR(s)/Issue(s)
#4162