Posts Tagged ‘testing’
Every once in a while, something happens in life that makes you say, “enough!”
That happened a couple of weeks ago to me and a couple other programmers working on the same project that I’m working on.
The issue was that we had made some significant changes to a project, we had communicated to the project manager that the changes required that the entire project needed to be retested, but the testing never happened. So of course we spent the next several days doing the “testing” and fixing.
This scenario should resonate with just about every programmer that reads this blog, but it should raise some questions as well.
Actually, I used this technique to automate submitting information to a set of web sites, but you could use this same technique to script any web site, including one you are currently developing, so that you can verify that the site actually does what it is supposed to do.
You might already have a testing tool that you use, so you might wonder why you’d want to use this technique.
By now, most people are familiar with the fact that ASP.NET will send mail from the codebehind by simply adding a few lines to your web.config file and adding another few lines of code in the codebehind file.
But it wasn’t until recently that I found that you don’t need to have access to an SMTP server to test your code.
It has always struck me as an odd practice to give a written test to an interviewee during the hiring process. I’ve been on both sides of the hiring process. I’ve had to take a few of these tests. My general perception is that all a test shows is that the person taking it knows how to take a test.
I’m going to approach this topic from the hiring manager’s perspective since that is the only perspective that really matters. I could go on about how it is unfair to me as a potential employee, but that wouldn’t convince those who need to be convinced. So here are some points to consider when considering testing as part of the process: