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.

Sign up for GitHub

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

Jump to bottom

Add a test for #106/#107 (coded test files with relative paths) #114

Open
aytey opened this issue May 29, 2024 · 0 comments
Open

Add a test for #106/#107 (coded test files with relative paths) #114

aytey opened this issue May 29, 2024 · 0 comments
Assignees
@Den1552

Comments

@aytey
Copy link
Member

aytey commented May 29, 2024 •
edited
Loading

To get this working, we need to hand-create a .tst file (that uses a relative path for the coded test file), import that, and then try to edit the coded tests.

See #106 and #107
@aytey aytey assigned Den1552 and unassigned Den1552 Jul 16, 2024
@Den1552 Den1552 mentioned this issue Aug 23, 2024
Merged
aytey pushed a commit that referenced this issue Aug 29, 2024
@Den1552
Added E2E for #114 (#183)
37d33d8 
## Summary

Added E2E for #114. 
Creating new TST that imports an coded test. Check in E2E if we can edit
the coded test with `// vmock` autocompletion.

## Added
`vcast_coded_tests_relative_path.test.ts` E2E test.
Added `import_coded_tests` spec group.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Den1552 Den1552

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aytey @Den1552