wikipedia about testware

Testware is a sub-set of software with a special purpose, that is, for software testing, especially for software testing automation. In this sense, automation Testware is designed to be executed on automation frameworks.


It includes artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.
Testware is produced by both verification and validation testing methods. Like software, Testware includes codes and binaries as well as test cases, test plan, test report and etc. Testware should be placed under the control of a configuration management system, saved and faithfully maintained.
Compared to general software, testware is special because it has: a different purpose;
different metrics for quality and different users


The different methods should be adopted when you develop testware with what you use to develop general software. Testware is also referred as test tools in a narrow sense.

Comments

Boedhie said…
Dear Ugne,

Hi, I'm Budi from Indonesia. I have worked as Software tester (like you) in Citibank N.A Indonesia. And i have blog too about software testing just like you (http://boedsoftest.blogspot.com), because i plan to join google adsense affiliation program.
Please visit my blog in your convenient time. Do you think google will approve my proposal?

Thanks for your attention
Regards,

Budi
budi.hutasuhut@gmail.com
4:16 AM
ugne said…
Nice blog, Budi. I am sure you will succeed with google.
3:26 AM
Post a Comment

Popular posts from this blog

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Read more

tester's day!

Happy testers day! Top 24 replies by programmers when their programs don't work: 24. "It works fine on MY computer" 23. "Who did you login as ?" 22. "It's a feature" 21. "It's WAD (Working As Designed)" 20. "That's weird..." 19. "It's never done that before." 18. "It worked yesterday." 17. "How is that possible?" 16. "It must be a hardware problem." 15. "What did you type in wrong to get it to crash?" 14. "There is something funky in your data." 13. "I haven't touched that module in weeks!" 12. "You must have the wrong version." 11. "It's just some unlucky coincidence." 10. "I can't test everything!" 9. "THIS can't be the source of THAT." 8. "It works, but it's not been tested." 7. "Somebody must have changed my code." 6. "Did you check for a virus on your system?...
Read more