Software Tester Fouls. Definition and Explanation

Sept. 20, 2011 - PRLog -- Software Tester fouls are actions that testers apparently not furthering the definitive purpose.
For example, if you uninstalled the browser and after that logged a bug that you could not access the Web community, that is a clear foul. You have accurately logged a bug, but it does not help make software better. So a tester must work with a degree of common sense.
Software Tester fouls mat be in all forms and scopes.
Another tester foul would be a bug that was entered where the tester describes that if the server gets uninstalled a user cannot access the service. Surely, the customer cannot access the service; the reason is the server is uninstalled.
The bug is not that the customer cannot access the service, but how the server got uninstalled in the first place. If the reason were not a security break, then this event might be a tester foul because technically the service is behaving properly, given that the server is uninstalled.
Many applications require that scripting be enabled in order to perform appropriately. If a user has script turned off in his browser settings and he wants to use this service, then the program is not expected to work appropriately.
A tester who spends time testing in this unsupported configuration is imprudent, and bugs logged against this configuration are tester fouls.
Don't waste time testing unsupported configurations, and bugs logged against such configurations are tester fouls. Nevertheless, the sage software tester might test another option.
Changing Security Zone Settings
There are 5 providential security zones in Microsoft's Internet Explorer:
•   Internet
•   Local Intranet
•   Trusted
•   Restricted
•   Local Computer
When you change the security zone settings from Low to High on the proper zone you can make problems in applications, especially if your application relies on ActiveX controls or any scripting. Because of these sorts of limitations, there might be a highest possible level of security on the zones supported by your application or there may be certain options that need to be turned on to permit the application to work. These settings need to be well documented not only for your customers, but also for the test and development teams.
Software Testers http://qatestlab.com/company/our-team/ can also foul in various other ways.
Championing a bug way beyond its time is a foul.
If you disagree with software bug http://qatestlab.com/services/sample-deliverables/bug-rep... resolution, then take it to your manager and clearly explain the issue and consider it with the spec writer, project manager, or responsible developer.
Do not reactivate the bug 5 times until somebody calls you a fool. Do not bother people or send email in all caps. These are ways that you get fouled.

# # #

QATestLab is independent, offshore software testing company located in Kiev, Ukraine. QATestLab performs testing of products on each stage of software development cycle.