Skip to content
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

feat: use 'testplane.config.[tj]s' config name #40

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

KuznetsovRoman
Copy link
Member

No description provided.

Comment on lines +4 to +7
TESTPLANE_NEW_TS: "testplane.config.ts",
TESTPLANE_NEW_CTS: "testplane.config.cts",
TESTPLANE_NEW_JS: "testplane.config.js",
TESTPLANE_NEW_CJS: "testplane.config.cjs",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Тут перечисляем список, чтобы кидать ошибку при попытке перезаписать имеющийся конфиг (проинициализировать testplane в проекте, где он уже есть):

Looks like .../my-project-dir already contains "testplane.config.ts".
Please remove old config or choose another directory.
Looks like .../my-project-dir already contains ".testplane.conf.ts".
Please remove old config or choose another directory.

@@ -12,7 +12,14 @@ describe("package", () => {
});

describe("initApp", () => {
[".testplane.conf.ts", ".testplane.conf.js", ".hermione.conf.ts", ".hermione.conf.js"].forEach(configName => {
[
".testplane.conf.ts",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can get names from CONFIG_NAMES constant instead of manually synchronizing them here

Copy link
Member Author

@KuznetsovRoman KuznetsovRoman Sep 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is good in source files, but i dont think it is in test files. I want small typo in CONFIG_NAMES to break these tests, so you would double-check it here

@KuznetsovRoman KuznetsovRoman merged commit 9d71ef5 into master Sep 30, 2024
3 checks passed
@KuznetsovRoman KuznetsovRoman deleted the TESTPLANE-263.config_name branch September 30, 2024 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants