Hi Abraham, Quoting Xavier (2020-08-24 10:36:09) > did you try to enable upstream test (`mocha test/test-*.js`) ?
Quoting Abraham Raji (2020-12-20 16:36:11) > I've made all the changes suggested by the team in the previous mails > except enabling tests. I ran the tests with the dependencies from npm > registry and they ran just fine. So it should be a dependency issue. When you write "it should be a dependency issue" is seems the tests do fail with the package. How does it fail? What is the error message? > Is it possible to upload the package without the tests for now? Possible, yes, but not wise. If the package fails its testsuite when packaged in Debian, then we cannot be sure that the package works when packaged in Debian. And even if it works today, then we will easily miss if it stops working due to changes in some of its dependencies. As a rule¹ of thumb, packages that fail their testsuite (or has no testsuite) should be targeted experimental. - Jonas ¹ I break that rule myself sometimes, and am then responsible for being extra attentive and fix any problems it might cause later on. Especially when you are new to packaging, I strongly recommend that you do *not* break the rule, because you rely on others to help you and therefore *cannot* fix it on your own if things go wrong later. -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
-- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
