-
-
Currently, our JS automated tests only run in nodejs environment in VMs provided by Travis CI. This is good, but not enough: it would be great to ensure that code we generate is compatible with multit…
-
While doing some load testing there was a mention by @provokateurin that the browser is using 3GB ram for the single tab.
Some things to clarify:
- What browser was used?
- Was it within the talk cal…
-
Device / Browser: PC + Chrome Production
Bug details / How to reproduce: I was testing a PR and noticed that the Delete button next to the selected image for the social media image does nothing.
Des…
-
`webgme-cli` uses plugins in the `webgme-engine` to generate files for plugins, visualizers etc... and the test suites use the `_globals` api provided by `webgme` to provide a range of well defined an…
-
We need to be able to test things like a new version of visual search or ckeditor automaticly. This is especially important as we move into new admin stuff. There are several options, we should pick …
-
We currently have no testing of what happens in the browser beyond some basic tests such as navigating the DOM during tests of largely server-side functionality.
We should have tests which carry ou…
-
I did this in class but was not marked
@thomasjbradley
-
The stubs currently don't return any value by default, which is fine in general, but connect/connectNative return a Port instance. It'd be nice if there was an easy way to get a prepared Port object, …
-
Example code:
```tsx
import { expect, test } from "vitest";
import { page } from "@vitest/browser/context";
import { render } from "vitest-browser-react";
import { HelloWorld } from "./fixtur…