The point of Tester
12-Feb-2006 12:58 Filed in: Tester
What does Tester do?
What does Tester not do?
What will Tester do in the future?
- Tester runs sequences of program code. Amazing.
- Tester runs sequences of program code loaded off disk. This code can be your own. Even more amazing.
- Tester does things in the background to store variables, that you can probe within your code, using a function called MARK.
- Using this function, you can also study program flow in your function, under different circumstances.
- It provides you with a multitude of bugs, since it is far from completed.
- Like most other REBOL apps, it runs on MacOSX, Linux and Windows without modifications. How many weeks of development did I just save?
What does Tester not do?
- Tester doesn't do profiling. It's not suited for performance testing.
- It doesn't improve your love life.
- It also doesn't store more than one fixed project on disk for now.
- Function marks can't be placed automatically.
- You can't yet watch variables inside objects
- It doesn't exist in its own context, so if you overwrite a Tester variable, it's likely to crash or go haywire.
What will Tester do in the future?
- Tester will be able to divide test sequences in stages, so you won't have to sift through 1500 lines of test code when editing very large cases. If you know how a multi-stage space rocket works, this is similar.
- Allow multiple projects.
- Allow you to import projects from other developers to set up a specific test suite in a snap.
- Let you set up expected results and compare those with the actual results from the test.
- Get a much cooler name than Tester.
- Exist in its own context, so it won't crash when the wind blows outside.
|