5f0a16c87c
- Closes #9599 - Implemented API for sending audit logs to the cloud on a background thread. - If the Postgres connection is opened through a datalink, its internal JDBC connection is replaced by a wrapper that reports executed queries to the audit log. - Also introduces `EnsoMeta` - a helper Java class that can be used in our helper libraries to access Enso types. - I have replaced the common pattern scattered throughout the codebase with calls to this 'library' to avoid repetitive code. - Refactored `Table.display` to share code between in-memory and DB - it was needed as the function stopped working for `DB_Table` after adding making the `Table` constructor `private`. - Clearer error when reading a SQLite database from a remote file (tells the user to download it first). - Follow up - correlate asset id of the data link: #9869 - Follow up - include project name (once bug is fixed): #9875 - Some problems/improvements of the audit log: - The audit log system is not yet ready for high throughput of logs #9870 - The logs may be lost if `System.exit` is used #9871 |
||
---|---|---|
.. | ||
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.