Reputation
10,613
Next tag badge:
71/100 score
29/20 answers
Badges
1 12 44
Newest
 Pundit
Impact
~349k people reached

Feb
10
answered Description field size limitation
Feb
10
answered Test data to test form input fields?
Feb
8
comment Test ideas for testing Reports?
Have you tried manipulating the data used to generate the reports? You could simplify it so that the output for each report is completely predictable, yet covers all the test cases.
Jan
18
answered How to differentiate myself from other Testers in the team?
Jan
5
comment Tracking manual testing interaction
This is a good answer. Many test automation tools have a Record feature. Their output scripts can provide a decent log of what was tested. I use WinTask, but you could certain try a bunch and see which works best for you. This might help: allthingsquality.com/2013/08/…
Jan
5
comment Tracking manual testing interaction
I have used TimeSnapper. It would be fine for the "screenshots" part, but doesn't actually "log" what is tested.
Jan
3
comment How to determine a 'reasonable' response time?
@dzieciou - Yes, that's one way. The other way is to "improve" A so that in the lab it's measurably faster than B. Then use A/B testing to find out if customers care, and if so, how much. I've done this in a server farm using smaller/slower servers compared to larger/faster servers with a load balancer in front. The web and application logs can help tell the results of the experiment, once analyzed.
Jan
3
answered How to determine a 'reasonable' response time?
Dec
22
revised What are good heuristics to generate testing time estimates as a percentage of development time
edited body
Dec
22
answered What are good heuristics to generate testing time estimates as a percentage of development time
Dec
22
comment What are good heuristics to generate testing time estimates as a percentage of development time
"I need to do this because testers/QA are often not consulted about the estimates used to bill customers for new projects they request" = big mistake.
Dec
16
comment A bug is fixed in Development environment but cannot be validated in Integration environment
It can always be validated in the integration environment. Perhaps more setup needs to be performed, perhaps a payment needs to be executed and then backed out. You need to decide if the validation is worthwhile or not. If not, just push it to Production and be ready to back it out quickly.
Dec
13
comment Evaluating severity of a defect of a reset button
In the context of your application, how important is this Reset button? You said it's now working as expected. What does the Reset button do now? Does it just do nothing? Does it wipe out the database? Does it crash the application? Does your shop have definitions as to how Severity and Priority are to be used? What are the defaults for Severity and Priority in your shop? Without knowing these - we cannot tell if "High" is appropriate or not.
Dec
3
awarded  Pundit
Dec
1
comment How do we create a “Test Incident” Report?
An incident may or may not represent a bug. Initially, it just requires investigation. A Defect/Bug report represents something that you believe is actually a bug. Note: some shops use the terms incident/defect/bug interchangeably. Most certification exams do not. You shop may have a local definition for the term "Test Incident".
Dec
1
comment How to find out which languages are supported by a website?
Ask your developers how the website/application determines the locale of the user. Ask them how they unit tested that feature. Then ask them the languages supported.
Nov
30
comment Examples for LOC figures, of test suites, and software projects?
You HP rep might be able to help.
Nov
27
answered Give read only access in Bugzilla
Nov
26
comment Should username/login ID be case-sensitive?
Case sensitivity adds more than a very thin layer to security. It expands the possible entries significantly, and consequently makes a brute-force attack more difficult.
Nov
24
answered Test Tool for our environment