The Seapine View

I got a call from a TestTrack TCM user who asked if you could schedule scripts to run on a continuous scheduled basis, rather than just once. I responded that you couldn’t, mainly because each test run represents a single execution of a test, not a continuous one.

I asked the user for more details in order to better understand the need. He revealed that his group does automated builds and wanted to launch tests after each build and log those results in TestTrack TCM. He wanted to incorporate TestTrack TCM with the automated build process and did not know how to.  So how do you do it? Well the answer will vary depending on your process.
Continue reading…

A smoke test (in software) is a quick test done after a build has completed successfully, but before QA fully tests it.

Microsoft claims that after code reviews, smoke testing is the most cost effective method for identifying and fixing defects in software.

Because the sooner we find a defect, the cheaper it is to fix it, we use a continuous build process utilizing QA Wizard Pro to automatically perform a smoke test each time a build finishes. This lets developers know right away if something that they checked in recently caused a problem.

Continue reading…