Commit graph

8 commits

Author SHA1 Message Date
Martin Pitt
a0f5432f4e Drop remaining vestiges of $LINT
This got removed in commit 15be883595.
2024-02-08 09:10:31 +01:00
Martin Pitt
5d2840449a Use Cockpit's shared static code checks
These will soon take over ESLint and stylelint, plus they also cover
ruff and other goodies for the Python part. This supersedes the explicit
ruff call.

This is already being used by cockpit-{podman,machines,navigator} etc.
2024-02-07 17:57:56 +01:00
Martin Pitt
ac77bafede Add ruff configuration
Apply our standard set of rules from our cockpit projects, and fix some
minor fallout:
```
test/check-application:7:1: I001 [*] Import block is un-sorted or un-formatted
test/check-application:9:119: E501 Line too long (122 > 118 characters)
```

Run ruff in CI to ensure we don't break it.
2023-09-22 10:42:05 +02:00
Subho
1c30b49d3d
Move from webpack to esbuild bundler 2023-04-12 10:23:20 +02:00
Allison Karlitskaya
03d02f398a build: add support for /pybridge scenario
Build the Python bridge from the cockpit project and install it into the
VM so we can run tests against it.
2023-02-01 17:40:48 +01:00
Martin Pitt
a937b82cd2 test: Bump Cockpit test API to 267, use --track-naughties option
run-tests recently got a new `--track-naughties` option [1] to explicitly
enable updating known issues on GitHub. Enable it for CI runs, and leave
it disabled for local runs and PackIt, as in these cases we don't want
to try and talk to GitHub.

[1] 7ef88e80ce
2022-04-19 13:14:21 +02:00
Martin Pitt
d544bda271 test: Use test scenario for selecting browser
Similar to what cockpit-composer does. This is rather simplistic, but
does fine until we need more complex scenarios.

Also use plain shell in test/run, there are no bashisms.

Closes #291
2020-03-10 17:52:30 +01:00
Martin Pitt
931e1be3c3 Add integration test using Cockpit test API
Closes #16
2018-03-09 10:13:03 +01:00