@@ -56,6 +56,39 @@ <h3>4. <code>project</code> (Optional)</h3>
56
56
use by passing the project name. or it will try to use the default project
57
57
</ li >
58
58
</ ul >
59
+ < h3 > 4. < code > includeTests</ code > (Optional, default: < code > false</ code > )</ h3 >
60
+ < p > Specifies whether to include test files for the element.</ p >
61
+ < ul >
62
+ < li >
63
+ NgVerse elements come with a full suite of tests to help ensure
64
+ reliability. However, including tests is optional for the following
65
+ reasons:
66
+ < ul >
67
+ < li >
68
+ < strong > Code changes may break tests:</ strong > < br />
69
+ After modifying an element, tests may fail because the behavior has
70
+ changed. In this case, you would need to debug and update the test
71
+ files, which can take extra time and effort.
72
+ </ li >
73
+ < li >
74
+ < strong > Test framework compatibility:</ strong > < br />
75
+ Our tests are written in Jasmine, so if you're using another framework
76
+ like Jest, the tests will not run at all.< br />
77
+ Therefore, tests are disabled by default.
78
+ </ li >
79
+ </ ul >
80
+ </ li >
81
+ < li >
82
+ If you want to include test files, use
83
+ < code > includeTests=true</ code > .< br />
84
+ Example: < code > ng g ngverse:add button --includeTests=true</ code >
85
+ </ li >
86
+ </ ul >
87
+ < p >
88
+ Keep in mind that we maintain and update our tests regularly. Tests are run
89
+ on every commit, merge, and release to ensure high quality. We take testing
90
+ seriously, so you don’t have to worry about test coverage! 🚀
91
+ </ p >
59
92
< h2 > Global Configuration</ h2 >
60
93
< p >
61
94
You can set a global configuration for the
0 commit comments