For Non coders:
Automated Black box testing basically strongly reduces the chances of things crashing, increases stability, and security. It specifically prevents regressions. I haven't seen any good tools to do this in IDE's.
Eclipse is a cross-platform development tool, that was founded by IBM, MERANT, QNX Software Systems, Rational Software, Red Hat, SuSE, TogetherSoft and Webgain. And is probably the only real competitor against Microsoft's and Apple's solutions.
For Coders:
Black box testing means that you treat a function as a box, and test the bounds of the parameters on it, and a few inside. You don't go and check each line of code. So: int ConvertToDogYears (unsigned int age, char * name), you would test 0,1, a few inside, large numbers, and max ages. In fact, you could also test NULL for name (because regardless if by design it might never receive NULL, it should still test for it).
I propose we make it possible to right click a function in eclipse, and set a few examples of inputs/results and a range to automatically test. This way, if all your functions parameter bounds and a few example tests. Some tests such as passing NULL pointers and seeing if it crashes could be tested too.
This would give us an automated way of testing for regressions, and could also help identify functions which are capable of segfaulting, or which buffer overflow.
The system can also automatically test the maximum values for C type variables, to ensure they are fine, and do tests automatically, such as pass NULL pointers and ensure that the function doesn't try to write to it.
Because if every function cant crash regardless of what is passed to it, it means that we will all benefit. And it means we will have a way for the compiler to test the program for us, and uncover bugs, which might take hackers to uncover (like passing a 3000 character string)
Tags:
(none)