What is at stake in this tutorial?
Who has been tested several times for other developers yab programs, get some experience. These experiences, I would like to write once, in the hope that this also for other will be interesting and helpful.
Tips for testing yab programs
- Error information always save or write down.
- The best way to start the test program still in the terminal, because once error information be issued when the program exits without a message.
- In order to make your work easier, you can while the app is running in the terminal, store all program informations automatically in a file.
| /path/to/the/Program > /boot/home/output.txt |
- Always remember all steps or "better" writing them down. The more detailed the messages are, so easier it is for the developer's to find the failure later. Especially in yab Programs are not always accurate error outputted to the position where it in the end of the Source code has occurred. This is because many of the processes running in a "loop". It is therefore very important to always know exactly when the error occurred. A simple Comment, stating at line number is xy error output is so and so, therefore, is mostly not sufficient.
- If the program crashed or has an error, do not merely describe from memory the error, generate possible first the process again. Be always sure that the error you describe is the same you name it.
- To be continued...
Made available by BeSly, the Haiku, BeOS and Zeta knowledge base.