We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

11

I probably first encountered this in the perl community, where the advice to use warnings "all"; and use strict; is so common. My guess is that I first read this in "effective perl programming" by Randal Schwartz - looks like it is on page 146. That book was published in 1998. I have had a lot of success with that approach for pointed and small programs, ...


10

One possibility here is to build into your testing the ability to flag a failure as a "Known issue" which is then reported with each run of your automation. I've gone into more detail in my answer to the question user246 linked - I'd recommend you check into my comments and the other responses there.


10

You should not edit the tests to pass. There are still defects in the product, and running the tests and having them fail on those points continues to provide data that the issues are not fixed. Since the development team has accepted the bugs and scheduled (although not solidly) them to be addressed, modifying the tests to no longer report the defects ...


8

I totally agree with Neils, and I'd like to address the question of whether or not this post belongs on this Testing site. Good testing starts long before any code is written, especially when it comes to the job of preventing error and simplifying future testing. Some basic testing principle apply regarless of the language used or application developed, ...


8

An early tool which generated warnings, with the intention to have them fixed by the programmer as if they were errors, was Lint. Stephen Johnson. Lint, a C program checker. Computer Science Technical Report 65, Bell Laboratories, December 1977. Reference shamelessly copied from: https://en.wikipedia.org/wiki/Lint_(software) Note that the mentioned ...


7

I would report the issue, but describe clearly that I cannot reproduce it. As a tester it is not my call to decide how much effort is put in reproducing the issue. I think we have signaling role. Risks Its nice if the report contains an estimated risk, do real users have problems and is it possible they get stuck and maybe cannot use a certain feature, ...


6

Two things can go wrong in this scenario: Button is not found (and thus you would have NullPointerException on method click()) so it will break before with NoSuchElementException. Button is not clickable (for some reasons) - and then you will have ElementNotClickableException. I'm not logging each step. I'm logging Exceptions on Framework level + doing ...


4

Yes, we use log monitoring as part of our testing process. Each manual tester is asked to monitor the logs during test (tail -f), to look for hidden errors/exceptions during testing. Also, our UI will pop-up a dialog if a client side exception is thrown. These usually cause automated tests to fail, and starts the investigation. Finally, we have a script ...


4

The problem should be reported, with a note in the report that you can't reproduce it consistently (or at all) and that you will update the report as more information is available. Your next steps should include some mix of the following strategies: If you can increase the level of logging, do so and leave the logging in place until you get a repeat of the ...


4

If anything, it was the reverse of this -- the culture started letting errors and warnings stay in, more and more. Back in punch card days, access to the punch card machines to read your deck of cards -- program -- was limited, often very expensive, and the deck often had to go through "verifiers," people who looked it over for errors. Even with a lightly ...


3

One part of the Ruby on Rails history over the last ten years is that frequently changes are marked with deprecation warning messages in one version before backward compatibility is removed altogether in the next version. So experienced folks in this community have learn to ignore those warnings at their peril. Over 30 years my personal experience has been ...


3

I wonder if it is relevant who said it first. I expect it historically to be more in line with many different teams running into similar issues with warnings and errors before they wrote it down as a rule in a book. Who said it first will probably be a lot of separate people in different programming teams around the globe. I think this is a logical rule each ...


3

I am working as a functional engineer in qa outsourcing company, where we provide qa services to the offshore companies. We work on both automation & manual testing and clients (Development Team) always ask us for the Crash logs, so that they can easily debug the issue. Following are the steps, that we follow to get the crash logs: Install iTools (...


3

Raise it anyway and give as much detail as possible (time, date, error log, test evidence, etc.). If it affects something further down the line, this will cover your back if a project manager or stakeholder asks why something wasn't done about it. I've experienced that a few times, where something's not reproducible so the developer just says "I can't fix ...


3

Globally, you want to determine the risk and take appropriate action (which may be no action). So you really want to know what the effect of the bug is, and how often and/or likely it occurs. If its rare and results on some minor UI anomaly, its not worth pursuing. If it happens every time on your landing page, or you're losing customer money, then at a ...


3

Report the bug. The developer(s) might not be willing or able to address the problem for one reason or another, but the developer(s) can't address the problem if it goes unreported. Give as much detail as you possibly can. I remember a bug I saw a few months ago which only occurred because the user was running Internet Explorer as a specific account in a ...


3

If the failing points are isolated solely to these low-priority issues, then you should leave them in place, and deal with these "known issues" showing up as fails. Make sure these "fails" are still reporting the same low-priority problem and not something bigger than originally reported. And check them over carefully. Often larger areas are blocked from ...


3

With Aspect Oriented Programming, you can use an annotation which executes Before (entering), After, or Around (before and after) a method. There isn't anything specifically designed to execute when entering a method, unless you used @After. For more information regarding the syntax and options, here is a link to Spring's online documentation: http://static....


3

Telemetry can't always pin point problems, but many times it can indicate the existence of a problem. If you expect some problems to occur you can sometimes add smarter telemetry and better analysis of other pieces of information, for example users skipping the Delete button and closing the application all together. A complementary approach is using A/B ...


2

GNU Utils for Windows seems to be the answer. It is not just grep. It's a full-featured set of command-line utilities, including: C:\SYSTEM>ls |grep "grep\|sed" agrep.exe egrep.exe fgrep.exe grep.exe sed.exe The main advantage of having native tools is compatibility; at any moment, you are ready to migrate your scripts to a *nix platforms with low ...


2

Do you just want to grep for the fun of it, or do you have specific types of tasks you want to accomplish? I end up using findstr.exe (built-in) for everything. Occassionally, I miss not having a better tool, but it works for me, and I bet I use it at least a dozen times a day.


2

Depending on what you want to do, one of these might be what you're looking for. Or, just searching for any combination of these will result in a number of "software comparision" articles that might list the one you're looking for: commercial: Splunk (wikipedia), LogScape Logwatch Swatch Octopussy Comparisons, lists: log management tools "build your ...


2

Web applications are a little bit different in that the web server deals with multiple, unrelated clients. If you are looking for a pattern, it is not enough to know that page Y followed page X -- you also need to know whether those events occurred in the same session. Sometimes this information is available in the logs; sometimes, not. Of course in a NAT'...


2

Three tips: 1. For logging this much detail, you can implement the WebDriverEventListener (as dzieciou already said in his comment). A great explanation is found on toolsqa. This will clear up your actual code to a great extent. 2. If you want other (further) things in your log, consider using helper methods for common actions. This will again greatly ...


2

Nothing to do with selenium for log parsing. you need to use java/perl/python which ever language your are using for writing selenium test scripts. But i implemented this kind of funtionality to check application logs. While implementing this you need to check following: 1. whether your application logs are generated with proper delimiters to indicate each ...


2

Practices of an Agile Developer, Subramaniam & Hunt, 2006. Page 137 has this... Just because your compiler treats warnings lightly doesn't mean you should. Treat warnings as errors. Checking in code with warnings is just as bad as checking in code with errors or code that fails its tests. No checked-in code should produce any warnings from the ...


2

Since you asked for anecdotal, this is about as anecdotal as it gets. This is a very opinion based question. First: Fix all warnings and errors. Do not tolerate any error messages Can be impractical, depending on the size/scope of an application. Some applications have many, many pieces, and you/your team are not in control of all of them. They will ...


2

Steve McConnell writes in Code Complete (1993): p69: Eliminate the causes of all compiler errors and warnings. Pay attention to what the compiler tells you about your code. A lot of warnings often indicates low-quality code, and you should try to understand each warning you get. In practice, warnings you've seen again and again have one of two possible ...


2

Summary: It's a reasonable concern but not one that I encounter in practice. Create smoke tests that are high level are assert that basic functionality, such as visiting the first page, work. These should not be reliant on OS specific peculiarities about edge cases. Run these tests as part of the deployment to an environment process and only consider the ...


1

This article provides the steps below for windows users Windows Vista/7 Users Open any Windows Explorer Window (My Computer, My Documents, etc.) Enter %appdata%, and press enter Navigate to Roaming > Apple computer > Logs > CrashReporter > Mobile Device > Device Name. (Note: your device name appears in iTunes on the left side, under 'Devices') You will see ...


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