Development Environments
Comparison chart of Integrated Development Environments.
Most everything I've tested in my career has been C++ code, but lately I've had a chance to work with some ActionScript based web hosted applications. I had a chance to look at one browser based application and I realized I have no idea what language it is written in!
Why does it matter? Well, look at this chart. Depending on the development environment, the challenges and advantages vary greatly. This means the risk of introducing bugs will vary to some extent by the attributes of the environment the software being tested was created in.
Have you found in your testing that the programming language or development environment used can accurately predict where bugs are introduced?
Most everything I've tested in my career has been C++ code, but lately I've had a chance to work with some ActionScript based web hosted applications. I had a chance to look at one browser based application and I realized I have no idea what language it is written in!
Why does it matter? Well, look at this chart. Depending on the development environment, the challenges and advantages vary greatly. This means the risk of introducing bugs will vary to some extent by the attributes of the environment the software being tested was created in.
Have you found in your testing that the programming language or development environment used can accurately predict where bugs are introduced?
The topic is undoubtedly very different and unique. But, wouldnt you be catering to only a particular section of testing professionals by this?
Reply to this
Hi Aarti,
Did you mean to comment on the Development Environments question, or the abstract on Reducing Test Case Bloat? It terms of Development Environments, I don't know enough to present a useful paper on that topic yet. I'd need more experience using applications written in languages other than C++. In terms of test case bloat, it doesn't apply to every tester, but I believe that it is a huge issue for most testers and test managers as dealing with existing test cases is pretty common. I think it would alienate only those testers who have all brand new code, but even those testers will soon have legacy test cases to deal with just as soon as they create them. Is there someone else it would leave out that I'm missing?
Reply to this