There's a very good chance you are currently undervaluing "Negative Tests." Tests designed to fail, and designed to exercise your error handling routines. These tests are VERY important as they execute code paths that are rarely executed. What if your error handler can crash!?
I was wondering about this for compiling. Say I write a container and I want to make sure it cannot implicitly copy. How do you write a test where success is not just failure, but failure to compile? How does it get protected from regression?
-
-
You attempt to build a TU that compiles it, and checks that the compiler reports error...
-
You can also attempt to do a static assert on a type trait for the type before going down the road of "code that's expected to not compile"
- Näytä vastaukset
Uusi keskustelu -
-
-
You can exercise this, to some degree, with SFINAE. Try to instantiate the wrong code path e.g. as a template-dependent lambda function and then see that a less specialized match got instantiated instead.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.