You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I use the npm test command defined as "test": "jest" in package.json to run my tests. The result on TeamCity server is standard text output, the same like without the plugin. The tests are also not included in TeamCity's tests results.
I also tried to set the environment variable in Windows TEAMCITY_VERSION (both as system variable and user variable), but when I execute npm test locally with this variable defined the output is still standard, not the TeamCity one.
Solution:
I found out that adding this configuration to package.json doesn't work anymore. It only worked for me when I added the configuration to jest's configuration file.
Environment: Windows 10
jest-teamcity version: 1.9.0
TeamCity version: TeamCity Professional 2020.2.4 (build 86063)
Issue:
I installed the npm package, added this to my
package.json
:and I use the
npm test
command defined as"test": "jest"
inpackage.json
to run my tests. The result on TeamCity server is standard text output, the same like without the plugin. The tests are also not included in TeamCity's tests results.I also tried to set the environment variable in Windows
TEAMCITY_VERSION
(both as system variable and user variable), but when I executenpm test
locally with this variable defined the output is still standard, not the TeamCity one.Solution:
I found out that adding this configuration to
package.json
doesn't work anymore. It only worked for me when I added the configuration tojest
's configuration file.I issued a PR with the documentation update: #20
The text was updated successfully, but these errors were encountered: