-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Content script tests #1066
Content script tests #1066
Conversation
7ec0d5d
to
3725e19
Compare
002a0ee
to
c4fa116
Compare
2d14b9d
to
f5ed649
Compare
f5ed649
to
eebb930
Compare
Can you integrate this into TeamCity? |
@phoerious It should be possible. I have zero experience with configuring TeamCity so it can take a while. |
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.
Why is the package-lock.json file so large now?
@droidmonkey Lots of dependencies in the packages 💁♂️ |
I hope we only need them for running the tests? |
@phoerious For tests yes. But those need to be downloaded also for the build script. I'm not aware of a method that could only download necessary dependencies per needed script. |
All tests files are copied to the extension before running them. Without this action the content scripts cannot be run. This also prevents including the tests files in the extension bundle. Those files cannot be included in the release.
It can be accessed manually from:
extension://<extensionId>/tests/tests.html
if the test script file is modified and the delete test folder action is deleted.Usage:
npm run tests
TODO:
Screenshot: