QA Blog Posts
QA Image Library
Check out the growing QA Image Library. This is my personal colleciton of Slack Images for that perfect QA Moment.
Jira Sprint Board Keyboard Shortcut
Atlassian Jira is popular with Software Development teams. It's used to track issues and tasks so that everyone knows what's going on.
Sprint boards are an important part of team planning. In an agile environment, sprint boards help make sure everyone is on the same page. There are three important views of a sprint board:
- Backlog - Issues that are planned for the next few sprints
- Active Sprints - Follow along as the developers make progress during the sprint.
- Reports - Detail information on how the project
To help navigate between the different boards, Atlassian created keyboard shortcuts. These would be good to memorize since it makes it quick to switch between the different board views:
1 - Backlog 2 - Active Sprint / Kanban Board 3 - Reports
When your view a Board, simply type '1' to go to the Backlog, '2' to the Active Sprint and '3' to see the Reports. This makes it handy when your doing sprint planning and need to switch between the backlog and the active sprint board.
Here's a handy chart reminder:
Hide That Bookmark Bar
Last week the Massachusetts State Police department posted a computer photo which contained a map of areas impacted by the recent Gas Explosions in Lawrence/Andover/North Andover. However, they didn't hide some private details:
When taking screenshots, you should always hide the Bookmark Bar. There is no need to add any distraction to your bookmarks.
Learn the Basics
- In Chrome, to hide the Bookmark Bar, simply type in Shift Command B.
- In Firefox, to hide the Bookmarks Toolbar, Go to View, then Toolbars, then deselect the Bookmarks Toolbar. (There is no keyboard shortcut in Chrome.)
Keyboard Maestro Tip
If you have Keyboard Maestro, you could always use this shortcut so that the Shift Command B works in any browser.
10 Tips for Effective Testing with Deadlines
Unless you're infinitely rich or prepared to rack up major debt, you need to budget your testing. Setting limits on how much you are willing to test helps control expectations. But what about your time? Do you budget your time or spend it carelessly?
Testing deadlines are the chronological equivalent of a budget. By setting aside a portion of time to complete a task, goal or project in advance you avoid over-spending. Deadlines can be helpful but they can also be a source of frustration if set improperly. Here are some tips for making deadlines work for QA:
- Use Parkinson's Law - Parkinson's Law states that tasks expand to fill the time given to them. By setting a strict deadline in advance you can cut off this expansion and focus on the important tasks.
- Timebox - Set small deadlines of 60-90 minutes to work on specific tests. After the time is up to your finish. This cuts procrastinating and forces you to use your focus on the task wisely.
- 80/20 - The Pareto Principle suggests that 80% of the value is contained in 20% of the input. Apply this rule to project testing to focus on that critical 20% first and fill out the other 80% if you still have time. This is an essential tip for when doing regression testing.
- Project VS Deadline - The more flexible your project, the stricter your deadline. If a task has relatively little flexibility in completion a softer deadline will keep you sane. If the task can grow easily, keep a tight deadline to prevent waste.
- Break it Down - Any project that has deadlines over one day should be broken down into smaller units. Long deadlines fail to motivate if they aren't applied to manageable units. It can also make testing more complex to manage.
- Hofstadter's Law - Basically this law states that it always takes longer than you think. A rule I've heard about software development is to double the time you think you need. Then add six months. Be patient and give yourself ample time for complex projects.
- Backwards Planning - Set the deadline first and then decide how you will achieve it. This approach is great when choices are abundant and projects could go on indefinitely. Figure out what the most challenges area will be for QA, and what things that will need to get done to have a successful test situation.
- Prototype - If you are attempting something new, test out smaller versions of a project to help you decide on a final deadline. For example, when testing multiple currencies, test known currencies first, before expanding to more complex exchanges.
- Find the Weak Link - Figure out what could ruin your testing and accomplish it first. Knowing the unknown can help you format your regression testing.
- No Robot Deadlines - Robots can work without sleep, relaxation or distractions. You aren't a robot. Don't schedule your deadline with the expectation you can work sixteen hour days to complete it. Deathmatches aren't healthy.
Strong Password Generator
Validating Password rules is a frequent job that QA has to handle. Fortunately there's help available, such as the Chrome Extension - Strong Password Generator by criticalthoughts8
With this extension you can easily generate strong and secure passwords. You can specify password length and used chars (lowercase, uppercase, numbers or custom). When you generate a password you can copy directly to your clipboard, or generate more of them and copy them all at one time (or select only which of them you want).
QA Thoughts about this Extension
- This is a great tool to test the various rules that may be imposed on passwords. You can make sure not only is the length is being checked, but that it contains numbers and mix letters.
- The extension keeps track of the password that is generated, just not on the site that it was generated for.
- You copy the password to the clipboard and paste it in the password box of the website. This makes it easy when you have to enter the password twice for validation.
- If your using LaunchBar, you can easily save the password as a snippet and reuse it for other applications.
- The extension is very simple and practical to use to validate the rules of a password field.
New QA Graphic Files
Once again, I have updated the QA Meme Library with more exciting graphics files. These are many common saying from the past couple of months that I feel is worth adding to the repository.
Check out the QA Meme collection for all six additions, here's a sample of three of them:
New Graphic Collection
When Patching something that can only be tested in Production:
I too like to live dangerously - From Austin Powers - The Spy Who Shagged Me
For those tickets where testing seems to be going on and on:
Maximum Testing Achieved
For those developers that like to write long test cases:
Don't use Seven Words when Four will do - Ocean 11
Know Any Other Graphics?
If there's any quote that you think should be added, let me know and I'll be sure to share it!
Page load time is an important part of QA testing. Browser Calories extension was created to help identify your site against the top sites on the internet. This is a great way to get a snapshot on what areas of your site you should focus on.
Description from the website
The web is getting fatter. If you take a look at the top 1 million sites, you will see that the median page weight is now bigger than SimCity 2000. Can you believe that?
Page weight is a super important metric and affects conversion, retention, and SEO. Actually, it not only costs user engagement â€" it costs money.
That's why Browser Calories exists. We will help you set a performance budget and measure if a page is exceeding these numbers or not.
Looks like even Google.com needs some tune up!
Cool Tool for your QA Toolbox
What's nice about Browser Calories is that you get a graphics that highlight the problem. This is useful to include in a Jira ticket so others can clearly see if the site needs to be tuned up.
This is also good as a benchmark to see if adding new library files will impact the overall performance of the site.
Getting Browser CaloriesBrowser Calories is available as an extension for Chrome, Firefox and Opera.
CodeCopy is an extension that makes it super easy to get code snippets from popular sites to your computer clipboard. As their slogan says, "Copy to clipboard buttons should exist on every code snippet.
CodeCopy puts an icon next to a code snippet, and when you click on the icon, it puts the code in your clipboard. No more fussing around making sure that you have all the code.
This helps QA and Engineering get the copy of the code. Useful for QA when you're looking for help when writing automation code.
Browser Badge Bookmarketlet
When taking browser screenshots, it's helpful to identify the browser that you're using. One way to highlight the browser is to put a browser banner in the browser before taking a screenshot.
Visit the QA Page to get all the banner image.
ChromeDrag and drop the "Chrome Banner" link to your bookmark bar to add a Chrome Banner overlay to any page your looking at.
FireFoxDrag and drop the "Firefox Banner" link to your bookmark bar to add a FireFox Banner overlay to any page your looking at.
Test Pilot in Firefox
Firefox likes to publicly test new features before deciding if they are worth fully integrating into the product. For QA, is a cool way to test upcoming features and see what's new. In addition, it's good to view the bug reports to get some fresh ideas on writing better bug reports.
Here are a few FireFox Experiments that might be useful for QA:
Notes in FireFox
One of the new features is Notes for FireFox, it's a way to jot down some notes on your FireFox account. You can access the notes by simply logging in. Using your Android smartphone device, you can jot some notes about testing and when you get to the office and log in you'll see the notes.
Unfortunately the Notes feature is not available for iOS. It works fine in Samsung Galaxy Tab E.
Check out the Bug Reports on github.
Side View allows you to view a mobile version of a site while browsing the web. This is useful when you want to watch a YouTube video and browse the web at the same time or apply something that you learn in the video.
Check out the Bug Reports on github.
Easy way to explain bug steps
Explainer is a Macintosh screenshot application that helps describing steps for a task. It's useful when trying to describe a bug or feature that doesn't work quite well.
In the free version, you only get 4 steps. For a one time fee of $7.99, you get 4 additional steps. The net results is a single professional looking image that can be mailed or added to any Jira issue.
Other features of the Pro version - the ability to save the documents - useful for repetitive tasks, change the watermark, lots more fonts for the description.
Four Things I Learned About Explainer
- You can use any screen capture application, or simply use Shift-Command-1 to use the built-in capture.
- The captured screenshots will be three times the size of what is shown in the step. This allows to reposition and resize screenshots.
- To type in the text simply hover the mouse over the bottom of each step, you'll see the overlay appear, click the text area and type away.
- You can Export the image to the Clipboard, Mail, Messages, Twitter, Facebook, Flickr, EverNote, and More. Don't see your option, add it in the Share Section of the System Extensions.
PostgreSQL Quick Cheat Sheet
If your use to supporting MySQL and now having to support PostgreSQL it can be tricky to know some of the common admin commands.
Here's a handy chart that I quickly put together of common admin commands that are used between the two databases:
|List databases||Show databases||l|
|Connect to database||use database;||c database|
|Show Database Tables||Show Tables||d|
|Show Tables Columns||Show Columns||d table|
If there are any other commands you want to add, let me know in the comments below.
July QA Graphics
Every once in a while I update the QA Graphic page with new content. This week I found a few images in my collection that I haven't posted yet.
I'll continue to look through my collection and upload images and add it to the collection.
If you have any graphics that you like to see, put it in the comment below or hit me up on Twitter.
Jira Short cuts for QA
Atlassian Jira is the most popular tool for teams to manage projects and track issues. Knowing shortcuts to navigate around the application can save you time with everyday tasks.
There are lots of great keyboard shortcuts, these are some of the ones that will improve your productivity .
Essential Keyboard Shortcuts
Here is a cheat sheet of essential shortcuts for Atlassian Jira that I believe are useful for any QA team.
This work any place in Jira:
|c||Create an Issue|
|m||Comment on the current issue|
|l||Edit issue label|
Quickly Navigate the Jira Board
I find using the One/Two combinations really handy when your looking at the Active Sprint and seeing what's in the backlog.
This is a useful bookmarklet to have:
data:text/html, <html contenteditable>
What this does is create a blank page where you can enter in text. It's a quick way to jot down some notes for test description or something.
Simply Drag and Drop this link to your bookmark bar to add this quick editor to your browser:
Now you'll have a simple text editor whenever you need to jot down a note or two.
Sometimes you need to test browser activity with slow connections. QA may need to test the user experience when it takes a long time for an image or JS file.
Chrome throttling is forcing the browser to slow down. This simulates a slow activity that users may experience via slow internet connections.
How to Enable Throttling
- Open the Developer Tools (Option-Command-I)
- Select the Network Tab
- Under the Audits Menu you should see Online with an Arrow to the right.
- There are two Presets, Fast 3G, Slow 3G, Offline
- You can create a Custom One by selecting Addx2026
Custom Throttling Options
Here are a couple of throttling settings to add.
- 56k - Modem Speed
- 128k - ISDN Speed
Handy Speed Chart
Here's a handy chart of various Internet Speeds:
A Few Words about Throttling Testing
Throttling testing is a good way to see what the page load looks like for some users. This is especially helpful when testing sites for mobile.
If you're running a Business to Business website, then running performance testing via throttling doesn't make sense since most users will be using fast internet.
Throttling testing is good for distance testing. (For example, if you have customers that are Japan, your website may not be performing as fast as people in New York City - because your servers are far away from their location.)