Hot answers tagged

45

As a developer with 15+ years experience, I'd say: please report the bug. I'd much rather have a ticket in the tracking system than a vague memory of a hallway conversation, or an interruption of what I'm working on. As Joel Spolsky put it: At any given time, I can only remember two bugs. If you ask me to remember three, one of them will fall on the ...


14

In my own experience, I've found that this really depends on the culture of the team or company that you're working with. On a team with good communication skills, and where everyone works together well, you may very well be able to just tell the developer about it, they take a look at it, and say it'll be fixed in 5 minutes. If it's longer, maybe ...


11

Do not discuss defects immediately with developers. Mainly because context switching is bad for their focus and could take up to 5-30 minutes to recover from. How to communicate a defect depends in which stage of development the defect is found. When I find a defects during testing of a task of the current iteration then I document the defect in the ...


11

We prefer to talk to developers first. Then, we together decide if detected error is a result of some quirk in processing and not even worth of bug, or, if it is worth a bug, we negotiate who will enter it to Bugzilla (we call if "buggify the feedback"). Often, developers prefer to write the bug description, because that way they can better describe the ...


7

Apart from obvious activities like test data creation, test case execution, bug reports...what other initiatives can a QA engineer , take which will help raise his value to the project/Client. You can only do what the situation and context permit you to do. In some shops testers get to review the Requirements before they are finalized. If that's ...


7

I imagine this would depend on the bug being raised. If it's a glaringly obvious bug (pages not loading, basic function not working, etc.) then I wouldn't waste a developer's time confirming it and do a write-up. However if I come across something that may be considered an edge case or I'm unsure of the intended functionality (mostly found during negative ...


7

Should Testers first discuss the bug with the developers before reporting it? From my experience in several different organizations I think the answer given the current question details is "it depends" It will depend on general factors such as: size of company size of development group current deadlines location of developers industry development ...


6

As a corollary to what David said, testers have the same memory limitations that developers do. If you don't log the bug, chances are very good it won't get fixed. This is especially true if it's not a severe bug, as chances are very good that the developer(s) are working on fixing severe problems first, and won't fix less severe ones for a while. And by ...


6

There will always be bugs that get past a tester and land in production. I have even had bugs that where in my face, we researched it, thought it was a fluke, because we couldn't reproduce it and then released the issue into production. The best thing you can do is learn from it and prevent the same in the future. I write an automated test-case for each ...


5

I think, it is always good to discuss things in person. You are lucky you have that things going on at your work place. In many companies all communication happens only via a system and that at times creates lot of confusion. What you write and what the other person understands may be completely different. For things like developers don't consider the bugs, ...


5

It depends... What is the overhead associated with reporting a problem? Some organization have big enterprisy processes, that requires lots of clicking, mandatory fields and multiple actors between the time a problem is open and the time everyone is done with it. You might also loose sight of important problems if they're drowning in a sea of minor (or ...


4

Definitely make a ticket. If the bug is "don't fix", you can refer another tester or developer who finds the same bug to the existing one, and save the developer some time. If the bug is a quick 5 minute fix, it still takes 5 minutes to do, and you have to remember to properly re-test. If these little distractions add up and are not documented, things ...


4

If the tester thinks that it is a defect, most likely it is a defect. The developer may be correct that the process is working as intended, in that case the defect is possibly in the documentation, user interface or testing plan. It should be logged, even if is testing error. This will lead to better determining where documentation deficiencies exist.


4

If there is possibility to discuss the bug, it could be valuable, for example you will have direct information of the cause and who will be the assignee of the bug. But generally it is not mandatory. It could be done as well after the bug is reported. Does not matter if you discuss the bug with developer or not, probably you will have to report the bug ...


4

It depends. Some of the factors I've found impact whether or not I report something formally or not: Development Methodology - If I'm working in an agile environment I'm more likely to work informally with the developer at first. In a waterfall environment, I'm more likely to report the issue because the developer has probably moved on to something else, ...


4

My view as a developer is that even if you are unsure it is a bug then report it. The upshot of this is (some of this has been mentioned by others) If you are unsure if it is a bug then you do not have enough product knowledge to perform the testing. This could be for several reasons, including partial training, poor documentation and insufficiently ...


4

If it is a clear and obvious breach against uncomplicated acceptance criteria, then report bug as soon as possible. Feel free to bypass the developer, BA or product owner. Otherwise, do not report the bug unless you first talk to the author of acceptance criteria (eg: BA or product owner), and the developer. If you do not: it is possible that you will ...


3

If my dev counterpart is available I try to talk with them first. That gives them the chance to request extra information that I might not have thought of. If my dev counterpart tells me that that area is not ready for testing, I tell them I will enter a bug just to remind myself to come back and look at the area once they believe it is ready. If I hear ...


3

Try to access the page on a slow network. Get a bad broadband connection with slow internet speed and load the page. It'll take some time to load the page and in the mean while if the page loader displays have celebrations with your team otherwise report a bug. You can also try connecting your mobile data to your laptop via hotspot or even via Bluetooth (if ...


3

While testing reports we need to take the following points into consideration - Input data validations eg. date ranges Format of the report Check if there are any calculations like total, max or min values Units are displayed correctly eg. currency Data is displayed correctly based on filters Page navigation and number of rows displayed per page Any links ...


3

You should aim to create the data yourself although whether you are doing manual or automated testing is a key factor and the following mostly applies to automated testing. One of the principles you should be looking to follow when performing automated testing is setup - execute - teardown Basically you want the system and most notably the data store to ...


2

Are you recommending the best/most appropriate way to test a problem? Are you thinking of scenarios or perspectives others arn't? Are you making sure you are seen as a valued asset within the team and not just a rubber stamp? What I must stress though, is that there is no "quick fix". The main thing is to build up trust and respect within the team. ...


2

Suggestions: Work on your writing and communication. You've asked two questions in your post, but haven't used question marks. Ellipses have three periods. Learn the difference between its and it's. Use an active voice in your writing. Speak to people more than you email or message. Conversely, don't socialize too much or waste other people's time. Find ...


2

Here are a few techniques I have seen used. ACH is a loose enough standard that an ACH that works for one financial institution will not necessarily work for another. If you have a particular financial institution in mind, they may be able to set up a test account for you. You can use ACH to move fictional amounts in and out of the test account. Lacking ...


2

Report the bug. A QA person's role is to be an independent verification authority. Someone who understands the products requirements and who is focused on quality. Make sure you document your problem scenario/reproduction steps so that your bug report stands up to scrutiny. The problem with discussing bugs ahead of logging them is that it introduces ...


2

Since I work at a team that doesn't have specific requirements for projects, I always communicate it with the developers and showing them how I reproduced the issue. They will acknowledge it. Sometimes they would say, let me check on that.. Coming back, they would say, oh I have fixed that please test it. Before they can fix it, I have already documented the ...


2

First and foremost, analyse how the bug got past you. Find a way of preventing this, and things like it from happening ever again. Second and maybe even more important, talk. Talk with everyone involved with getting new functionality out. As soon as requirements materialize, get your test approach on paper and scrutinize it AS A TEAM. That a harmful bug got ...


2

You need to verify following things: Verify the downloaded report is in correct format for example if you select pdf option then pdf should get downloaded and not html or other Verify the name of downloaded file is as expected, many a times file has some naming conventions which are followed Verify the header and footers if any Verify the calculations ...


2

This question has been asked many times before on this forum. So you should try to research a bit before adding this question. Take a look at Here where there is a list of good thinking tools and techniques mentioned for improving your practical thinking ability. You can start by reading the number of books mentioned here You can also follow many of the ...


1

To stay simple, and echo what others have said- (20 years experience here)... Find the steps to reproduce Take your screen shots or grab logs, etc. Find the root cause if you can Report the bug. Get it in the system. Perhaps do some limited searching to make sure it isn't a duplicate. speak to the developer at this point or when first able <-fin-> :)



Only top voted, non community-wiki answers of a minimum length are eligible