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
The unit tests we have today test specific sets of inputs such as "Compute position of G02 at time t and compare to sp3 precise position".
Property-based testing takes this approach a step further. It allows us to formulate tests of the type "For a test within the set of existing satellites, and for a time within t0 and t1, the error between broadcast and sp3 position is always lower than 10 meters".
The testing framework then tries to find test inputs within the set of admissible inputs that break the code.
The unit tests we have today test specific sets of inputs such as "Compute position of G02 at time t and compare to sp3 precise position".
Property-based testing takes this approach a step further. It allows us to formulate tests of the type "For a test within the set of existing satellites, and for a time within t0 and t1, the error between broadcast and sp3 position is always lower than 10 meters".
The testing framework then tries to find test inputs within the set of admissible inputs that break the code.
See e.g. https://semaphoreci.com/blog/property-based-testing-python-hypothesis-pytest
The text was updated successfully, but these errors were encountered: