fern-reporter
fern-reporter copied to clipboard
guidewire-oss
A ginkgo test reporter extension for storing test run information and also for reporting html pages
Once the fern client has been moved to a different repo, the server should be able to accept gRPC input so that the fern client can use protobufs to speed...
Update the tests in utils package to include `utils_test.go` and `utils_suite_test.go`, following Ginkgo's recommended [testing structure](https://onsi.github.io/ginkgo/#adding-specs-to-a-suite).
- Should upgrade to dockerhub with correct release version and use a guidewire org - If dockerhub is not possible in time, push to github package repository
Currently graphql api for `testRuns` API does not support pagination and returns all testRuns from the DB. As the data in DB grows this could prove problematic and expensive as...
- In the embedded HTML report view, "Total Tests", "Executed Tests", "Passed/Failed" fields are not updated dynamically. It just displays 1 by default. Attached screenshots for the same.
- Add screenshots, include sample post requests that could be used by the developer to use fern
When we click on insights page on the server, create a second tab that is able to use prompt engineering, send data and graphql schema over to chatgpt and get...
Add references to the fern-ui and fern-ginkgo-client projects in the README.md so that people understand the projects in the ecosystem as well as know what these individual projects are for...
The client should be using an auth scheme for sending information to the fern server The creds could be used to identify the authorized test projects
Metadata
Owner
Metadata
A ginkgo test reporter extension for storing test run information and also for reporting html pages