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
-[Test different node versions](#test-different-node-versions)
14
15
-[When are my changes going to be public?](#when-are-my-changes-going-to-be-public)
@@ -110,6 +111,18 @@ On VsCode, create a [_JavaScript Debug Terminal_](https://code.visualstudio.com/
110
111
111
112
We at this project have E2E tests. They are handy to test production-like scenarios and to have confidence in your changes.
112
113
114
+
## Smoke test
115
+
116
+
We conduct a series of small and pragmatic e2e tests called the **smoke test**. This test is essential for testing the package's core functionality.
117
+
118
+
Using the smoke tests, we composed a series of more elaborate tests. Such as:
119
+
120
+
-**Compatibility Observability Test**: Scheduled test to verify daily if our package is working with the `latest` version of nx
121
+
-**Backwards Compatibility Test**: To verify if the current changes work correctly with the supported versions of nx that we are committed to maintaining (see [Compatibility overview with Nx
It's essential to handle the libraries' build before running these tests. These tests will use whatever is in the dist folder. This is done using the build closest to the actual build on the NPM registry.
125
+
113
126
## Continuous Inspection (SonarQube)
114
127
115
128
We have continuous inspection for each PR that is made; we use SonarQube for this. It will suggest some changes, detect code smells in your changes and, security recommendations. We encourage implementing the changes that Sonar offers.
0 commit comments