Description
Software testing is important to find the bugs, improve software quality and meet user's needs, etc.
TAPoRware tools use user specified text, pattern, word lists and so on as inputs. Tool developers have no control of the quality and format of these inputs. The tester should imagine as much as possible user scenario so that the tools can respond properly.
Basic Practices
Functional testing
- test whether each tool performs correctly, including input validation and expected results.
Input testing
- test if tool can handle text irregularities and poorly formated inputs.
Multi-platform testing
- test if tool can act and display properly in different platforms (i.e. operating systems and web browsers).
Performance test
- for large corpus, help developers to find the bottleneck and optimize the corresponding code.
Reporting Problems
We appreciate reports of problems even if we don't fix them immediately. If in using or testing a tool you come across a problem or suggested improvement we recommend the following:
- Register? for a TADA wiki account so you can edit the tool page and add a line about the problem right in the documentation.
- E-mail Kamal Ranaweera at kamal dot ranaweera at ualberta dot ca with the problem.
- Try to be specific:
- What text did you use (if you can, e-mail it to us)
- What tool and settings did you use
- Check the TAPoRware General Problems to make sure you haven't encountered a known general problem.
- Remind us of the problem (gently).
If you can program we can send you the code, if you would like to try to fix it yourself.
--
LianYan - 29 Nov 2005
