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
it's great to see some unit tests coming into the project! As there are not too many tests yet, I was curious how much thought had been given to the test framework? Over on a branch of epanet-dev, I started adding a tests under the CMake framework https://github.com/bradleyjeck/epanet-dev/tree/structure-for-testing
An advantage of using CMake is that it does not introduce another dependency like Boost. Of course Boost and other frameworks have their own advantages. Just thought it might be worth opening the topic while making a change is easy.
The text was updated successfully, but these errors were encountered:
Hey @bradleyjeck - did you mean to post this on the EPANET project?
RTX uses BOOST already so I wouldn't view this as an extra dependency. That also answers the other question about how much thought went into it -- since BOOST is an existing requirement, and is header-only, I figured it would be easy to integrate.
Hi @samhatchett - thanks for the feedback. Posting here was intentional as I was curious about the choice for this project. RTX has good reasons for Boost which is great. That may attract other related projects like EPANET in the same direction.
it's great to see some unit tests coming into the project! As there are not too many tests yet, I was curious how much thought had been given to the test framework? Over on a branch of epanet-dev, I started adding a tests under the CMake framework https://github.com/bradleyjeck/epanet-dev/tree/structure-for-testing
An advantage of using CMake is that it does not introduce another dependency like Boost. Of course Boost and other frameworks have their own advantages. Just thought it might be worth opening the topic while making a change is easy.
The text was updated successfully, but these errors were encountered: