Timeline for Boundaries of unit testing between my code and a library or sub-component
Current License: CC BY-SA 3.0
32 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 15, 2023 at 23:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 16, 2022 at 23:53 | history | protected | gnat | ||
| Dec 16, 2022 at 22:06 | answer | added | kollegah | timeline score: 1 | |
| Oct 24, 2022 at 21:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 26, 2022 at 20:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 26, 2022 at 19:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 29, 2021 at 18:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 1, 2021 at 18:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 1, 2021 at 17:16 | answer | added | ndp | timeline score: 0 | |
| May 29, 2021 at 3:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 29, 2021 at 2:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 1, 2020 at 1:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 3, 2020 at 0:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 4, 2020 at 0:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 6, 2019 at 23:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 8, 2019 at 22:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 8, 2019 at 22:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 9, 2019 at 21:25 | answer | added | Craig Noah | timeline score: 0 | |
| Nov 11, 2017 at 4:12 | history | tweeted | twitter.com/StackSoftEng/status/929200207077826560 | ||
| Jul 12, 2017 at 0:02 | comment | added | Christopher Regner |
Alright, first, I think I finally understood the idea that BDD isn't necessarily coupled to UI. But I still have no idea how to do this while testing React components as a front-end developer: Keep your business logic in a business library that doesn't have any dependencies on UI.
|
|
| Jul 11, 2017 at 23:14 | comment | added | Christopher Regner | Looks like I got confused with methodologies and approaches of testing React components. I'll do a review and then get back to this post after. Thanks! | |
| Jul 11, 2017 at 22:48 | comment | added | Andy | At any rate, testing methodology isn't related to the fact that you don't want your business logic in the UI; that's an architecture issue, and has nothing to do with your testing methodology (which is why I am commenting instead of answering). | |
| Jul 11, 2017 at 22:42 | comment | added | Andy | Not sure where you got that idea, that sounds off to me. MSpec for example is a BDD framework. Its mostly a shift in your thinking about how to build the unit test. Integration / acceptance tests may involve the UI, but nothing in BDD to me suggests it has to involve the UI. en.wikipedia.org/wiki/Behavior-driven_development | |
| Jul 11, 2017 at 22:21 | history | edited | Christopher Regner | CC BY-SA 3.0 |
added 186 characters in body
|
| Jul 11, 2017 at 22:16 | comment | added | Christopher Regner | Hmm, my understanding is that in BDD, in order to test the behavior, you inevitably involve the UI, this is what I've observed in JS front-end development. | |
| Jul 11, 2017 at 21:31 | comment | added | Andy | Keep your business logic in a business library that doesn't have any dependencies on UI. An N-layer, DDD, onion, whatever you want to call it approach. | |
| Jul 11, 2017 at 21:29 | comment | added | Christopher Regner | What would be the better approach? | |
| Jul 11, 2017 at 21:09 | comment | added | Andy | I'd avoid testing 3rd party library code in general. Your approach concerns me though because you're coupling your validation (which is business logic) to a specific UI. Change UIs (or even to another library) and it seems like you'll be throwing your business logic away. | |
| Jul 11, 2017 at 20:33 | history | edited | Christopher Regner | CC BY-SA 3.0 |
added 141 characters in body
|
| Jul 11, 2017 at 6:54 | review | Close votes | |||
| Jul 26, 2017 at 3:02 | |||||
| Jul 11, 2017 at 3:20 | history | edited | Christopher Regner | CC BY-SA 3.0 |
added 36 characters in body
|
| Jul 11, 2017 at 3:14 | history | asked | Christopher Regner | CC BY-SA 3.0 |