-
Notifications
You must be signed in to change notification settings - Fork 245
fix(e2e): actually test the packaged app when running npm run test-packaged #6558
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
Conversation
| export const context = parsedArgs as CommonParsedArgs & | ||
| Partial<DesktopParsedArgs & WebParsedArgs>; | ||
|
|
||
| debug('context:', context); |
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.
Handy for seeing if it actually picked up all the command-line args it should have.
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.
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.
It's printed already a few lines down with secrets removed from the list:
const contextForPrinting = Object.fromEntries(
Object.entries(context).map(([k, v]) => {
return [k, /password/i.test(k) ? '<secret>' : v];
})
);
debug('Running tests with the following arguments:', contextForPrinting);
Is this print doing something different?
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.
Sorry didn't see it. We can remove it again.
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.
I just merged it #6561

Edit: This seems to only affect npm run test-packaged, not npm run test-packaged-ci which is what we run in CI. So it was fine in CI, just not locally. Depending on which command you run locally.
Since the refactor a couple of months ago we've been passing too many
--to the app and the arg parser was missing--test-packaged-appso it would re-build compass every time.You can test this by running the E2E tests against the locally installed beta, dev or GA like this: