-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
show test logs in CI #157
base: main
Are you sure you want to change the base?
show test logs in CI #157
Conversation
@@ -6,16 +7,16 @@ import { matchesFixture } from './assertions.js'; | |||
import { copyFixture } from './fixtures.js'; | |||
import { createAddon, createTmp, install, runScript } from './utils.js'; | |||
|
|||
const DEBUG = process.env.DEBUG === 'true'; | |||
const debugLog = debug('addon-blueprint:temp'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
temp feels like a goofy label
import { type Options, execa } from 'execa'; | ||
import fse from 'fs-extra'; | ||
import fs from 'node:fs/promises'; | ||
import os from 'node:os'; | ||
import path from 'node:path'; | ||
import { fileURLToPath } from 'node:url'; | ||
|
||
const DEBUG = process.env.DEBUG === 'true'; | ||
const debugLog = debug('addon-blueprint:utils'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
addon-blueprint:test-utils
maybe? To not suggest users they get debug output when running the bp itself, since this is only effective when running the bp's tests...
more work to be done
this will give me more confidence which tests are actually being run in CI, especially since there is a lot of "skipped" tests in the output (because of the way that vitest works)