michael-kerscher
4ec257942e
Tests for playground are using a mock response ( #2611 )
...
The official playground quite often provides a timeout error as in
https://github.com/google/comprehensive-rust/issues/2549
This is mocking/overriding the response from the playground for success
and failure messages to avoid the server provided timeouts. As far as I
see most responses from the playground are delivered below 10 seconds
(but varies a lot...)
There still might be timeouts and I know of the following knobs that can
be tuned
- wdio waits for 10 seconds until it aborts the current attemp (e.g. to
wait for the text to be as expected)
347de61d13/tests/wdio.conf.ts (L98)https://github.com/webdriverio/webdriverio/issues/14090 which would
allow for an immediate mock response without waiting for the remote
endpoint)
347de61d13/theme/book.js (L31)
2025-02-06 12:33:33 +01:00
michael-kerscher
153bd63cc0
tests: rename to generic-page.test.ts as only *.test.js is tested ( #2625 )
...
the filename without .test. was introduced in #2621
2025-02-04 08:19:53 -05:00
michael-kerscher
2cf9a35b23
Check if menu bar buttons are display and functionality works ( #2621 )
...
Test the main page for existence of
- theme button visible
- clicking shows the list of themes
- search button visible
- and tests successful search for "Welcome"
- language button visible
- clicking shows the list of languages
this is testing functionality missing in dev environments in
https://github.com/google/comprehensive-rust/issues/2588 and is relevant
for https://github.com/google/comprehensive-rust/issues/2620
2025-02-04 10:36:34 +01:00
dependabot[bot]
7f712b5292
Bump undici from 6.21.0 to 6.21.1 in /tests in the npm_and_yarn group across 1 directory ( #2580 )
...
Bumps the npm_and_yarn group with 1 update in the /tests directory:
[undici](https://github.com/nodejs/undici ).
Updates `undici` from 6.21.0 to 6.21.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/nodejs/undici/releases ">undici's
releases</a>.</em></p>
<blockquote>
<h2>v6.21.1</h2>
<h1>⚠️ Security Release ⚠️ </h1>
<p>Fixes CVE CVE-2025-22150 <a
href="https://github.com/nodejs/undici/security/advisories/GHSA-c76h-2ccp-4975 ">https://github.com/nodejs/undici/security/advisories/GHSA-c76h-2ccp-4975 </a>
(embargoed until 22-01-2025).</p>
<h2>What's Changed</h2>
<ul>
<li>fix(<a
href="https://redirect.github.com/nodejs/undici/issues/3736 ">#3736</a>):
back-port 183f8e9 to v6.x by <a
href="https://github.com/ggoodman "><code>@ggoodman</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/3855 ">nodejs/undici#3855</a></li>
<li>fix(<a
href="https://redirect.github.com/nodejs/undici/issues/3817 ">#3817</a>):
send servername for SNI on TLS (<a
href="https://redirect.github.com/nodejs/undici/issues/3821 ">#3821</a>)
[backport] by <a
href="https://github.com/metcoder95 "><code>@metcoder95</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/3864 ">nodejs/undici#3864</a></li>
<li>fix: sending formdata bodies with http2 (<a
href="https://redirect.github.com/nodejs/undici/issues/3863 ">#3863</a>)
[backport] by <a
href="https://github.com/metcoder95 "><code>@metcoder95</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/3866 ">nodejs/undici#3866</a></li>
<li>[Backport v6.x] fix: Fixed the issue that there is no running
request when http2 goaway by <a
href="https://github.com/github-actions "><code>@github-actions</code></a>
in <a
href="https://redirect.github.com/nodejs/undici/pull/3877 ">nodejs/undici#3877</a></li>
<li>types: [backport] Update return type of RetryCallback (<a
href="https://redirect.github.com/nodejs/undici/issues/3851 ">#3851</a>)
by <a href="https://github.com/metcoder95 "><code>@metcoder95</code></a>
in <a
href="https://redirect.github.com/nodejs/undici/pull/3876 ">nodejs/undici#3876</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/nodejs/undici/compare/v6.21.0...v6.21.1 ">https://github.com/nodejs/undici/compare/v6.21.0...v6.21.1 </a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="e260e7bb17c3acc6050b2414bc9f7dhttps://redirect.github.com/nodejs/undici/issues/3851 ">#3851</a>)
(<a
href="https://redirect.github.com/nodejs/undici/issues/3876 ">#3876</a>)</li>
<li><a
href="be8cd0afa0ee6176cd2ehttps://redirect.github.com/nodejs/undici/issues/3863 ">#3863</a>)
[backport] (<a
href="https://redirect.github.com/nodejs/undici/issues/3866 ">#3866</a>)</li>
<li><a
href="a0220f14bfhttps://redirect.github.com/nodejs/undici/issues/3817 ">#3817</a>):
send servername for SNI on TLS (<a
href="https://redirect.github.com/nodejs/undici/issues/3821 ">#3821</a>)
[backport] (<a
href="https://redirect.github.com/nodejs/undici/issues/3864 ">#3864</a>)</li>
<li><a
href="353ab63188https://redirect.github.com/nodejs/undici/issues/3736 ">#3736</a>):
back-port 183f8e9 to v6.x (<a
href="https://redirect.github.com/nodejs/undici/issues/3855 ">#3855</a>)</li>
<li>See full diff in <a
href="https://github.com/nodejs/undici/compare/v6.21.0...v6.21.1 ">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores )
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/google/comprehensive-rust/network/alerts ).
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-01-22 03:58:31 -05:00
Martin Geisler
1c709efac0
Remove flaky JS test ( #2551 )
...
This should stop the test failures, but of course it won’t fix the
underlying problem.
Reverts part of #2513 . Related to #2549 .
2025-01-15 09:28:57 +01:00
michael-kerscher
34920c76e6
tests: hello world playground run with success and failure tests ( #2513 )
...
Implement two tests for the rust playground:
- successful run of the hello world example with the hello world message
in stdout and a hidden stderr
- on purpose compilation error is shown in stderr and "No output" in
stdout
2025-01-14 10:44:23 +01:00
michael-kerscher
48b2b5c312
Add a test framework to test the JS part of the course ( #2471 )
...
This is a first draft for a test framework for testing the JS part of
the book that is discussed in #2462
It is using [webdriverIO](https://webdriver.io/ ) and the webdriverIO
[Expect API](https://webdriver.io/docs/api/expect-webdriverio/ ) in
combination with [Mocha](https://mochajs.org/ ). WebdriverIO is taking
care of accessing the webpage with a real browser and can access the
state of the page so behavior can be asserted.
Currently only a small test for the speaker-notes implementation demos
the functionality.
The [Static Server
Service](https://webdriver.io/docs/static-server-service/ ) is used to
serve the book in a way that the test runner can access it.
A CI integration can look like https://webdriver.io/docs/githubactions/
and is implemented with a headless setup. In CI it uses the language
variable to set environment variable that configures where the built
book should be mounted from
---------
Co-authored-by: Martin Geisler <martin@geisler.net>
2024-12-04 09:06:58 +00:00
