Closed jeffjakub closed 9 months ago
apollo-smith
to generate random data sets to verify we can compose supergraphs and generate query plansRegarding unit tests, I would ask that we strive to not drop existing unit tests in the federation
repo when moving to Rust. (Or at least, I've seen a few rewrites in the past where folks say they'll port the tests over later, and later never comes.)
Regarding performance tests, we should at least take performance samples from customers who have complained about performance issues or are expecting performance improvements (not sure if we have a list of these) along with test harness graphs that have been habitually slow (we currently only collect a little data here, but we could start collecting more).
Regarding the test harness, it shouldn't be too painful to start running both JS and Rust versions of code, assuming we allow compiling to WASM. (We could also do without WASM, but it would be a bit more work.)
Yes, let's leverage @clenfest's recent work for the worker-server as much as possible.
We have a pretty good testing strategy figured out. Closing this in favor of more specific items.
As an engineer, I would like to:
So that we have quality metrics established at the start of the project to establish a baseline.
Acceptance Criteria