Testing for Beginners

#1

Post by brycecolquitt » Mon, Nov 26, 2012, 7:23 PM UTC

Testing for Beginners
blog.enoughtobedanger.us

Re: Testing for Beginners

#2

Post by gailees » Mon, Nov 26, 2012, 7:47 PM UTC

Thank you. I've used Codeacademy, Coursera, Udacity, edX, and while all of them do a somewhat decent job teaching me how to program, I've totally missed the boat on testing.

Re: Testing for Beginners

#3

Post by CobaltHex » Mon, Nov 26, 2012, 8:05 PM UTC

By the way, in the first example you have "should be able to subtract (1-1)" (not verbatim) but is 2-1 in code

Re: Testing for Beginners

#4

Post by nbashaw » Mon, Nov 26, 2012, 9:01 PM UTC

CobaltHex wrote: post #3

By the way, in the first example you have "should be able to subtract (1-1)" (not verbatim) but is 2-1 in code

Whoops! Thanks for catching that

Re: Testing for Beginners

#5

Post by bcbrown » Mon, Nov 26, 2012, 9:55 PM UTC

I don't really like that you call tests "just checklists". That's accurate for unit tests, but I don't think it really captures the spirit of integration or functional tests.

Integration tests, to me, provide value by making a space to brainstorm "what if" questions around corner cases of interactions between components. Testing the "happy path" provides confidence that all the individual assumptions aren't inconsistent as a whole.

Functional tests, for me, provide a way to think about "well, this is what we built, and it's internally correct, but is it what will fit the needs of our users?" I would also differentiate between end-to-end scenario testing, and discrete testing of a single unit of functionality. An example of the former would be the signup process, while the latter might be making changes in a preferences configuration screen.

I think it would be worthwhile to also discuss "tenet" testing, such as Performance, Accessibility, Localization/Internationalization, Failover/Rollover, Security.