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
Just wondering if it's a good idea to write tests for this Symposion -- it has 0% test coverage if I am not missing the something obvious. It does seem like a pretty big project to write tests for though. It seemingly passed the real life tests of being used for several conferences over the years without many hiccups..
The text was updated successfully, but these errors were encountered:
I was wondering about writing some tests, at least for the parts that we write and change.
We might get more bang for our buck with some selenium tests just to make sure that the major application flows work, though unit tests might be easier to feed back upstream.
Just wondering if it's a good idea to write tests for this Symposion -- it has 0% test coverage if I am not missing the something obvious. It does seem like a pretty big project to write tests for though. It seemingly passed the real life tests of being used for several conferences over the years without many hiccups..
—
Reply to this email directly or view it on GitHub.
Just wondering if it's a good idea to write tests for this Symposion -- it has 0% test coverage if I am not missing the something obvious. It does seem like a pretty big project to write tests for though. It seemingly passed the real life tests of being used for several conferences over the years without many hiccups..
The text was updated successfully, but these errors were encountered: