Re: Acceptance testing with Clojure
Possibly, I don't know off the top of my head though. On Mon, Sep 29, 2014 at 2:13 AM, Adrian Mowat wrote: > Thanks for pointing out prism - it's just what I needed. > Is there any way to add colours to the output so I can easily see if a test > failed? > On Sunday, 28 September 2014 15:34:39 UTC+1, Ashton Kemerling wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> I can answer this in two ways: >> >> 1. Acceptance testing Clojure code. >> 2. Acceptance testing other code with Clojure. >> >> I have significantly more experience with the latter than the former. >> >> All in all, I prefer the built in clojure.test library over more >> opinionated libraries like Midje. In particular I recommend adding in >> Aphyr's excellent Prism plugin to your profiles.clj to do auto >> testing, and pjstadig`s similarly excellent humane-test-output for >> readability. >> >> My dislike of midje stems from how awkward I found it to share setup >> code between tests. I feel that clojure.test nests more, allowing me >> to save more code up front. I also haven't used Midje in a while, so >> Brian might've upgraded it without me noticing. >> >> You also cannot go wrong with test.check. I really enjoy using it for >> both correctness and simple profiling (e.g. print to console and see >> if anything gets too slow). >> >> On the latter front, test.check + JDBC/Selenium/HTTP appears to be one >> of the most fruitful ways of hunting down bugs in single-page >> applications that I've ever seen. I think at this point the bug count >> for our testing code is close to 5 for an average of 3 hours per bug. >> Most of these bugs were either concurrency, caching, or SQL based, and >> some were close to 4 years old. I'll be giving a talk on this subject >> at the Conj this year, and the video will be posted later if you >> aren't attending. >> >> For more info on test.check, you should check out Reid Draper's >> Cognicast episode >> ( >> http://thinkrelevance.com/blog/2013/11/11/reid-draper-cognicast-episode-045) >> >> and my Cognicast episode >> (http://blog.cognitect.com/cognicast/ashton-kemerling-064) >> >> On 09/28/2014 08:24 AM, Ruslan Prokopchuk wrote: >> > I've googled around a little bit, but didn't found any relevant >> > info about subject. Please, share your experience about acceptance >> > testing with Clojure! >> > >> >> - -- >> Ashton >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1 >> >> iQIcBAEBAgAGBQJUKBxtAAoJEIkUqIW02x05kBMQALUcIDvGO+ohCVUJw2xC2HMT >> UPBK3eFHVhrgp84EqFx00A/+/sFmXM6wKWzcbTuEeG4YEuiea2UiZjqs7bFvqg3w >> L2j3CwGpG+eENSP4CQ4L2qB0n4ljuWSqHgH1eWYIGC98f6hKfMC2Itb7SEKWdm1M >> iYTQdFKhULbsmahwL1Z+dKuxe9Q6Vv20HahQan5T7JY8jE8QJI5d/icXI8xel6OV >> 3wlsW1AfBec1d7r/67R0MRnWqD2swE3WFbh+SlNQz/orSNvHvOLufhS5s0Xamtji >> xo59pX7xrAMkyf/a40HopHTcWD1Qkp9T0VBO0X43dfdbTH5gMdc7iOFmpHXj5EAi >> wbRRAtXp75F6tdYHf4n6I9y+N2auRz1SF1KOPb69mjkjx8Pujy8EwZdfpwABqLtu >> 4D06KlRrVmCiduvc0eVBcUVOa0o2lait2y0cMLa1M2Tt3rwNZb23nrJ3T9xXhrIY >> GKW/N+uQ2uC028Wqh3oFcOrjN6S6XU6rahhojCSSXsfMddmzsgz6qPdy3voAa68j >> e4Z/aP5Q9fPViW3j/E9FGmrQU89eOUdPVabbrJNu2J3DqGu3eaRLpAJP9oa5v7Q+ >> iEOGU38ZbLwMXhvw8VvMOnF9MKn9JAsoDZOPFOfuftZWmP1q0HqmBxxxg4WBW3hC >> 2EldloS4hNyaSJ4tIlex >> =djIk >> -END PGP SIGNATURE- >> > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Acceptance testing with Clojure
Thanks for pointing out prism - it's just what I needed. Is there any way to add colours to the output so I can easily see if a test failed? On Sunday, 28 September 2014 15:34:39 UTC+1, Ashton Kemerling wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I can answer this in two ways: > > 1. Acceptance testing Clojure code. > 2. Acceptance testing other code with Clojure. > > I have significantly more experience with the latter than the former. > > All in all, I prefer the built in clojure.test library over more > opinionated libraries like Midje. In particular I recommend adding in > Aphyr's excellent Prism plugin to your profiles.clj to do auto > testing, and pjstadig`s similarly excellent humane-test-output for > readability. > > My dislike of midje stems from how awkward I found it to share setup > code between tests. I feel that clojure.test nests more, allowing me > to save more code up front. I also haven't used Midje in a while, so > Brian might've upgraded it without me noticing. > > You also cannot go wrong with test.check. I really enjoy using it for > both correctness and simple profiling (e.g. print to console and see > if anything gets too slow). > > On the latter front, test.check + JDBC/Selenium/HTTP appears to be one > of the most fruitful ways of hunting down bugs in single-page > applications that I've ever seen. I think at this point the bug count > for our testing code is close to 5 for an average of 3 hours per bug. > Most of these bugs were either concurrency, caching, or SQL based, and > some were close to 4 years old. I'll be giving a talk on this subject > at the Conj this year, and the video will be posted later if you > aren't attending. > > For more info on test.check, you should check out Reid Draper's > Cognicast episode > ( > http://thinkrelevance.com/blog/2013/11/11/reid-draper-cognicast-episode-045) > > and my Cognicast episode > (http://blog.cognitect.com/cognicast/ashton-kemerling-064) > > On 09/28/2014 08:24 AM, Ruslan Prokopchuk wrote: > > I've googled around a little bit, but didn't found any relevant > > info about subject. Please, share your experience about acceptance > > testing with Clojure! > > > > - -- > Ashton > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQIcBAEBAgAGBQJUKBxtAAoJEIkUqIW02x05kBMQALUcIDvGO+ohCVUJw2xC2HMT > UPBK3eFHVhrgp84EqFx00A/+/sFmXM6wKWzcbTuEeG4YEuiea2UiZjqs7bFvqg3w > L2j3CwGpG+eENSP4CQ4L2qB0n4ljuWSqHgH1eWYIGC98f6hKfMC2Itb7SEKWdm1M > iYTQdFKhULbsmahwL1Z+dKuxe9Q6Vv20HahQan5T7JY8jE8QJI5d/icXI8xel6OV > 3wlsW1AfBec1d7r/67R0MRnWqD2swE3WFbh+SlNQz/orSNvHvOLufhS5s0Xamtji > xo59pX7xrAMkyf/a40HopHTcWD1Qkp9T0VBO0X43dfdbTH5gMdc7iOFmpHXj5EAi > wbRRAtXp75F6tdYHf4n6I9y+N2auRz1SF1KOPb69mjkjx8Pujy8EwZdfpwABqLtu > 4D06KlRrVmCiduvc0eVBcUVOa0o2lait2y0cMLa1M2Tt3rwNZb23nrJ3T9xXhrIY > GKW/N+uQ2uC028Wqh3oFcOrjN6S6XU6rahhojCSSXsfMddmzsgz6qPdy3voAa68j > e4Z/aP5Q9fPViW3j/E9FGmrQU89eOUdPVabbrJNu2J3DqGu3eaRLpAJP9oa5v7Q+ > iEOGU38ZbLwMXhvw8VvMOnF9MKn9JAsoDZOPFOfuftZWmP1q0HqmBxxxg4WBW3hC > 2EldloS4hNyaSJ4tIlex > =djIk > -END PGP SIGNATURE- > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Acceptance testing with Clojure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can answer this in two ways: 1. Acceptance testing Clojure code. 2. Acceptance testing other code with Clojure. I have significantly more experience with the latter than the former. All in all, I prefer the built in clojure.test library over more opinionated libraries like Midje. In particular I recommend adding in Aphyr's excellent Prism plugin to your profiles.clj to do auto testing, and pjstadig`s similarly excellent humane-test-output for readability. My dislike of midje stems from how awkward I found it to share setup code between tests. I feel that clojure.test nests more, allowing me to save more code up front. I also haven't used Midje in a while, so Brian might've upgraded it without me noticing. You also cannot go wrong with test.check. I really enjoy using it for both correctness and simple profiling (e.g. print to console and see if anything gets too slow). On the latter front, test.check + JDBC/Selenium/HTTP appears to be one of the most fruitful ways of hunting down bugs in single-page applications that I've ever seen. I think at this point the bug count for our testing code is close to 5 for an average of 3 hours per bug. Most of these bugs were either concurrency, caching, or SQL based, and some were close to 4 years old. I'll be giving a talk on this subject at the Conj this year, and the video will be posted later if you aren't attending. For more info on test.check, you should check out Reid Draper's Cognicast episode (http://thinkrelevance.com/blog/2013/11/11/reid-draper-cognicast-episode-045) and my Cognicast episode (http://blog.cognitect.com/cognicast/ashton-kemerling-064) On 09/28/2014 08:24 AM, Ruslan Prokopchuk wrote: > I've googled around a little bit, but didn't found any relevant > info about subject. Please, share your experience about acceptance > testing with Clojure! > - -- Ashton -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUKBxtAAoJEIkUqIW02x05kBMQALUcIDvGO+ohCVUJw2xC2HMT UPBK3eFHVhrgp84EqFx00A/+/sFmXM6wKWzcbTuEeG4YEuiea2UiZjqs7bFvqg3w L2j3CwGpG+eENSP4CQ4L2qB0n4ljuWSqHgH1eWYIGC98f6hKfMC2Itb7SEKWdm1M iYTQdFKhULbsmahwL1Z+dKuxe9Q6Vv20HahQan5T7JY8jE8QJI5d/icXI8xel6OV 3wlsW1AfBec1d7r/67R0MRnWqD2swE3WFbh+SlNQz/orSNvHvOLufhS5s0Xamtji xo59pX7xrAMkyf/a40HopHTcWD1Qkp9T0VBO0X43dfdbTH5gMdc7iOFmpHXj5EAi wbRRAtXp75F6tdYHf4n6I9y+N2auRz1SF1KOPb69mjkjx8Pujy8EwZdfpwABqLtu 4D06KlRrVmCiduvc0eVBcUVOa0o2lait2y0cMLa1M2Tt3rwNZb23nrJ3T9xXhrIY GKW/N+uQ2uC028Wqh3oFcOrjN6S6XU6rahhojCSSXsfMddmzsgz6qPdy3voAa68j e4Z/aP5Q9fPViW3j/E9FGmrQU89eOUdPVabbrJNu2J3DqGu3eaRLpAJP9oa5v7Q+ iEOGU38ZbLwMXhvw8VvMOnF9MKn9JAsoDZOPFOfuftZWmP1q0HqmBxxxg4WBW3hC 2EldloS4hNyaSJ4tIlex =djIk -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Acceptance testing with Clojure
I've googled around a little bit, but didn't found any relevant info about subject. Please, share your experience about acceptance testing with Clojure! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
