The thing that's surprised me so much is that there are two departments development and testing. In one department programs are written and automated tests are written to test them every time a build is run, in the other department programs are used and then tests are written to check the things that have been found will automatically be picked up the next time a build is run.
Now correct me if I am wrong but isn't there a massive intersect in these primary functions?
Don't take my word for it
I just read a blog and in there it states"...your responsibility as the God of Programming is also to be the God of Testing..."The blog does state this is how good developers deal with bad code, so does it mean that those developers that don't also try to be good testers aren't good? Interesting thought in a world where so many people assume anyone in testing is looking for a way to become a developer!

No comments:
Post a Comment