Skip to main content
12 events
when toggle format what by license comment
Aug 25, 2020 at 12:59 comment added Slam You need to define "unit" for yourself. It's quite common in python to treat public api or "entry point" as a unit. Main reason for this – implementation details should be easy to refactor. Covering underlying functions in isolation is rather bad practice – if it's not public API, nobody should care about changes. So write tests from top perspective, maximize coverage, add low-level testing, if you need to simulate really rare edge case
Aug 5, 2020 at 15:59 history protected gnat
Jul 29, 2020 at 12:00 history tweeted twitter.com/StackSoftEng/status/1288444193199796225
Jul 22, 2020 at 10:03 vote accept Jossy
Jul 22, 2020 at 9:18 answer added Flater timeline score: 46
Jul 22, 2020 at 8:41 comment added Flater @gnat: This question seems to suggest to combine unit and integration tests, not about having both kinds of separate test suites.
Jul 22, 2020 at 7:37 comment added Jossy I guess I'm hypothesising that if the data is exactly aligned then you get an integration test from a series of unit tests...
Jul 22, 2020 at 7:36 review Close votes
Jul 27, 2020 at 3:03
Jul 22, 2020 at 7:29 comment added Jossy I think it's a good thread and one I'd not read before - after reading it there seems to be a case for unit and integration tests both being needed. I guess my question still stands though - how closely do you couple the fixtures used by unit and integration tests?
Jul 22, 2020 at 7:18 comment added gnat Does this answer your question? Do I need unit test if I already have integration test?
Jul 22, 2020 at 7:06 review First posts
Jul 25, 2020 at 5:11
Jul 22, 2020 at 7:06 history asked Jossy CC BY-SA 4.0