Files
nomad/ui/testem.js
Phil Renaud 4b91c17dfa [ui, ci] retain artifacts from test runs including test timing (#24555)
* retain artifacts from test runs including test timing

* Pinning commit hashes for action helpers

* trigger for ui-test run

* Trying to isolate down to a simple upload

* Once more with mkdir

* What if we just wrote our own test reporter tho

* Let the partitioned runs handle placement

* Filter out common token logs, add a summary at the end, and note failures in logtime

* Custom reporter cannot also have an output file, he finds out two days late

* Aggregate summary, duration, and removing failure case

* Conditional test report generation

* Timeouts are errors

* Trying with un-partitioned input json file

* Remove the commented-out lines for main-only runs

* combine-ui-test-results as its own script
2024-12-03 09:56:06 -05:00

60 lines
1.6 KiB
JavaScript

/**
* Copyright (c) HashiCorp, Inc.
* SPDX-License-Identifier: BUSL-1.1
*/
// @ts-check
'use strict';
const JsonReporter = require('./test-reporter');
/**
* Get the path for the test results file based on the command line arguments
* @returns {string} The path to the test results file
*/
const getReportPath = () => {
const jsonReportArg = process.argv.find((arg) =>
arg.startsWith('--json-report=')
);
if (jsonReportArg) {
return jsonReportArg.split('=')[1];
}
return null;
};
const config = {
test_page: 'tests/index.html?hidepassed',
disable_watching: true,
launch_in_ci: ['Chrome'],
launch_in_dev: ['Chrome'],
browser_start_timeout: 120,
parallel: -1,
framework: 'qunit',
reporter: JsonReporter,
custom_report_file: getReportPath(),
// NOTE: we output this property as custom_report_file instead of report_file.
// See https://github.com/testem/testem/issues/1073, report_file + custom reporter results in double output.
debug: true,
browser_args: {
// New format in testem/master, but not in a release yet
// Chrome: {
// ci: ['--headless', '--disable-gpu', '--remote-debugging-port=9222', '--window-size=1440,900'],
// },
Chrome: {
ci: [
// --no-sandbox is needed when running Chrome inside a container
process.env.CI ? '--no-sandbox' : null,
'--headless',
'--disable-dev-shm-usage',
'--disable-software-rasterizer',
'--mute-audio',
'--remote-debugging-port=0',
'--window-size=1440,900',
].filter(Boolean),
},
},
};
module.exports = config;