Timeline for Should I bother to write unit test for UI/UX Components?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2014 at 12:20 | review | Close votes | |||
| Apr 20, 2014 at 3:01 | |||||
| Apr 11, 2014 at 16:13 | answer | added | Jason Boyd | timeline score: 7 | |
| Apr 8, 2014 at 20:11 | history | tweeted | twitter.com/#!/StackProgrammer/status/453626085251358720 | ||
| Dec 9, 2013 at 14:39 | comment | added | ozz | @RobertHarvey I think he is asking whether UI test tools like Selenium is enough | |
| Dec 9, 2013 at 13:57 | answer | added | Kyle Johnson | timeline score: 0 | |
| Aug 6, 2013 at 15:14 | audit | Suggested edits | |||
| Aug 6, 2013 at 15:15 | |||||
| Aug 5, 2013 at 19:09 | comment | added | Robert Harvey | Is it still worth the effort to write unit test for UI/UX Components where UI tests would be able to pick up everything the unit test would plus also do a better job since it can test what is actually rendered? -- No. That's why UI testing frameworks exist. How would you unit test a UI anyway? | |
| Aug 5, 2013 at 17:55 | history | asked | ryanzec | CC BY-SA 3.0 |