testing infrastructure online
So to be clear we already have testing infrastructure along with deployment pipelines. The testing suite is phpunit (comes backed in with the frameworks we’re using.) the Continuous testing environment is Travis-ci and automated security scanning is done with snyk.io.
Continuous deployment is baked into the community grid platform and deploys images the Dallas Makerspace Docker hub
As for selenium testing that’s something we may look into later.
We’re literally at the point of going over the build log and fixing those bugs reported. From what I’m seeing about 90% of it is just stupid formatting / convention bugs that slipped in from key board cowboying features. Another 5% is just code quality stuff like documentation. The rest are code coverage and things like:
160 | ERROR | [x] Expected "int" but found "integer" for parameter type
162 | ERROR | [ ] Expected "bool" but found "boolean" for function return type