c72cef305d
* Stop validating optional Data Link fields * Fix incorrect default value in Datalink input * Stop `Autocomplete` fields from opening automatically without `autoFocus` * Increase E2E test timeout * Fix E2E test race condition? * Fix error message for empty string input * Highlight active Datalink input * Show description when Datalink input is invalid * Fix Datalink input unfocusing when errors appear * Fix `enso://` path error text * Fix hover display of autocomplete items * Move `Autocomplete` tooltip above Dropdown container * Update Enso path validation * Update test file and Enso File datalink regex --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Bypassing failing tests. |
||
---|---|---|
.. | ||
data | ||
polyglot-sources/enso-test-java-helpers/src/main/java/org/enso | ||
src | ||
package.yaml | ||
README.md |
This is a set of tests for the Base
library for Enso.
HTTP tests
The run test suite for the HTTP component requires an active helper server on
the localhost. If it is present, the port it listens to should be provided by
setting the ENSO_HTTP_TEST_HTTPBIN_URL
environment variable to a value like
http://localhost:8080
. The URL may contain a trailing slash.
To run the test server, you may use the following command:
sbt 'http-test-helper/run localhost 8080'
You can stop the server via Ctrl-C.
See the server's documentation for more information.
Cloud tests
By default, a subset of cloud tests runs whenever the
ENSO_HTTP_TEST_HTTPBIN_URL
environment variable is set, using a mock of parts
of the cloud logic running on the helper server.
To run a full set of cloud tests against a real deployment, you need to set the following 3 environment variables:
ENSO_CLOUD_API_URI
to point to the root of the cloud API,ENSO_CLOUD_CREDENTIALS_FILE
to be a path to a file containing the credentials to use, e.g.~/.enso/credentials
,ENSO_RUN_REAL_CLOUD_TEST=1
to tell the test suite to run against a real cloud deployment.
Note that some cloud tests (e.g. testing secrets in HTTP requests) still require
the ENSO_HTTP_TEST_HTTPBIN_URL
setup, even if running against a real cloud
deployment.
Testing audit log batching
Currently, we only have a manual scenario for testing that log messages are actually batched.
To test it, launch the http-test-helper
with additional
--enable-manual-log-batching-test
flag. For more information, see the comment
on batchingTestModeEnabled
in
PostLogHandler.java.