Wednesday, July 15, 2015

Software Testing QA Resources

Software Testing Resources and Downloads:
All in one resource for software testers – The biggest resource of software testing books, software testing templates, QA testing interview questions and answers, testing QA training, automation testing tools, software testing tutorials, software testing pdf, software testing material, QA videos, software testing certification guides, and much much more..
I thought it would be helpful to create a resource page that you can always refer for your software testing needs. I’ll add to it as I learn more. I recommend sharing this with your friends and bookmarking it for your reference and convenience. Enjoy and make a better testing career!


Software Testing Templates:

Sample Bug Reports : Here you can find software bug report samples for web projects as well as desktop applications.
Test plan Sample : Use this software testing test plan template as a reference to create test plan for your project. This test plan should give you good idea about how to write effective test plan. This is a sample test plan for Payroll system project.
Test case template : This template will guide you on how to write test cases and what are the fields required while writing test cases. You can add or modify this template fields as per your project needs.
Premium Test Case Template  Test Case document is by far the most used document in STLC. Use this template to write and manage test cases effectively. Download this template on this page.
Software Testing Templates:You will find 50 software testing templates on this page.You can buy all these 50 templates for very cheap price. Testing templates includes Test plan, UAT plan, Test Cases templates, Status report, Change control log, Risk log, Test report, Unit test plan and many more important software testing templates.

Software Testing Books:

Testing and QA Books: On this page I have listed popular software Testing and Quality Assurance books. You can note down these books for reference or buy these books from amazon.
*Best Software Testing Career Package eBook:  A Software Tester’s Journey from Getting a Job to Becoming a Test Leader!”
The Most Helpful, Practical and Inexpensive Software Testing Study Guide. Stop yourself trying to figure out how to succeed in your software testing career. Instead, take benefit of these proven methods and real-life examples.
This is a Complete Manual Testing Course with Practical Tips on Job Hunting, Career Planning and Testing Skill Improvement!
Manual Testing Help Free eBook – Visit the page to get this incredible software testing ebook (version 1 and 2). It got some good information to learn fundamentals of software testing.
I’ll suggest you to go through these ebooks as it is helpful to understand the basic software testing concepts. Also this is important to quickly brush up your testing knowledge if you are preparing for a software testing interview.
Ebook to Prepare for Software Testing Interview – One more free ebook – If you are preparing for software testing interview this is useful book for you. Check out the page to see the list of topics covered in this ebook. You need to follow the easy three step process to download this free ebook. NOTE – If you already subscribed to our newsletter you just need to search the first confirmation email you got after subscription and you will get your password to download this ebook as well.
More Books:

Software Testing Training:

Best Software Testing Online training Course: Most Practical, Precise and Inexpensive Software Testing Training Course: Software Testing (Basics + Advanced) + Automation Basics.
It is going to include everything there is to know for you to become a perfect Software Tester. See more details about this course on above page.

Software Testing tools and Tutorials:

Learn QTP in 25 Days : These QTP tutorials are designed for beginners to advanced users. Starting from QTP basics you will learn advance scripting all with practical examples for your easy understanding.
Learn Quality Center in 7 Days : with 25+ in-depth QTP tutorials we have received many requests to cover HP Quality Center tutorials. This will be HP ALM/QC test management software online training in 7 in-depth tutorials.


Software Testing Training Course Videos: Software testing course demo and Day 1 sessions.
LoadRunner Video Tutorials : HP LoadRunner Tutorials – Learn LoadRunner with these simple tutorials.

Software Testing Interview Preparation:

101+ Software Testing Interview Questions: Tips to prepare testing interview, qa interview questions, ISTQB and CSTE certification questions and some mock test to judge your testing skills.
QTP Interview Questions and Answers part 1 : In this post we have covered some useful tips to prepare for QTP interview along with top 20 common and crucial Quick Test Professional questions and answers.
QTP Interview Questions and Answers Part 2 : This covers most of the basic and advanced questions asked by the readers which are helpful for freshers as well as experienced candidates. So check if your question is completely answered or not.
Tips to Handle Any Job Interview Successfully : No matter which career path you want to choose below are the best tips to help you land your dream job. Job Interview Tips and advice Applicable for Any Job Seeker Looking for a Dream Job.
Software Testing QA Resume : How to Write a Killer Software Testing QA Resume That Will Turn Into an Interview Call. I’m sure after reading this article you will be able to write a killer flawless software testing and quality assurance resume that will definitely turn into an interview call.
Software Testing Interview Tips : Preparing For Software Testing Interview – Simple Tips To Follow Prior And at The Time of Interview. The whole article is a very general discussion about the challenges that a tester has to face in an interview.
How to prepare for software testing interview : What you need to know about software testing? You should make interviewer feel that it was a complex application you were testing and had lot many challenges in it for a tester – here is how.
How to Get a Software Testing Job as a Fresher : This post will cover what you should and should not do to get your first job as a testing professional.

Software Testing Jobs:

List of some useful software testing job sites with hundreds of testing QA jobs. Use site’s job search functionality to search jobs by category or keywords. To use these testing job sites make sure to specify the location of your job search. Also create your account on these sites with latest updated resume and apply for only relevant jobs.

ISTQB Study Guide:

ISTQB sample papers and tipsAre you planning to take any of the ISTQB exam? We have the largest set of sample question papers that there is a huge chance that your next ISTQB paper will be from this set only. Provide your email address on above page to start getting these papers, exam tips and study material in your inbox.
*ISTQB Premium Study Material: Complete ISTQB Certification Premium Study Package – “Confidently Appear and Pass the Foundation Exam Easily with Our Comprehensive Premium Study Material”
We are introducing the premium ISTQB study material – ISTQB dumps and study guide that we never shared before. This is a combined efforts of last 6 months by STH team. The material is verified by certified ISTQB experts and many students who actually used this material for passing the exam with high scores. You can also quickly revise the important ISTQB topics before the exam with the help of this study material.
ISTQB certification sample question papers with answers:
ISTQB Exam Latest Sample Question Papers with Answers:

CSTE and CSQA Certification Study Guide:

CSTE certification exam sample papers:
CSQA Certification Guide 1:  CSQA Certification Preparation Guide – Part 1
This is an article for all those who have always wondered what CSQA was about and wanted to know more about how to approach it or whether to approach it or not.
CSQA Certification Guide 2: CSQA Certification Sample Questions with Answers and More Tips – Part 2

BFSI Domain Resources:

BFSI Domain Resources: Many Readers asked for the BFSI domain documents in comment section of post How Domain knowledge is Important for testers. Listed below are some resources on BANKING, FINANCIAL SERVICES AND INSURANCE DOMAINS.
  • How Bank Works: This site is targeted to banking operations and communities. You can read new articles on banking domain and banking services.
  • Insurance Domain articles: You can download the Insurance industry white papers from this web page. Each month you can read new insurance topic from insurance industry experts.
  • Banking and Financial news: Here you can find latest BFSI Domain events and articles.
Web Terminology guide: A useful resource for web application testers. Covers all basic and advanced web terminologies like TCP/IP, HTTP, Web servers, client servers, cookies, client and server side scripting, CGI and much more..

Why Bug Reporting is an Art - that should be learned by every tester !!

What happens when you report an issue? I threw another piece to think.
  • Developer resolves it
  • Sometimes they do not resolve it
  • Sometimes they delay fixing the issue
  • Sometimes issue is marked as “Not Reproducible”
Good, but why developer does not resolve or delay fixing or mark the issue as “Not reproducible”?
After a pause, the most interesting phase of brainstorming started – discussion.
Presenting here some excerpts from the discussion:
As a tester, it’s our primary responsibility to test the application or product and report the issues. But mind well, the responsibility really does not end here. Actually, from here, the real duty starts. It’s very important to understand why your bugs are being rejected or being marked as “not reproducible” and how do you react to it.
Bug reporting and tracking is an art, a fine art where by applying some fine points, we can change the quality of product from downside up and can win the trust of client. No matter at which level of hierarchy you are sitting, being in software testing, it’s necessary that you master the skill of bug reporting. Bug reporting is not a document but a summary report about what is going wrong, how it is wrong and where it is wrong. Bug report is an enveloped bad news about application and how you present it, is crucial in deciding the future of that bug.
You must have read about what information a bug should have and which fields should be included. But what about overall bug report? Even after including every necessary field, you might not be able to create a good bug report.
From my experience, I have listed out some points to be taken care while reporting a bug. I have provided example for each point to make it more graspable.
Let’s consider an e-commerce website selling car parts and accessories. I have described some of the relevant issues with“should not be” and “should be” columns for each point below.
Have a look:
#1. Read the bug you just reported and ask yourself – are you able to understand it?
Not able toAble to
Title: Application is very slowTitle: Performance of application is poor on some specific pages.
Steps to Reproduce: Whenever user tries to buy something, he finds that the response is slow and sometimes not able to take the required action.Steps to Reproduce: Some specific pages of the application, i.e. Car models, new arrival, and accessories taking more than 15 seconds to load
#2. Provide proximity of reproducible to save time and efforts
Should not beShould be
Title: Application crashes on payment pageTitle: Application crashes every time, on payment page for a specific selection
Steps to Reproduce : Whenever user selects payment option, application crashesSteps to Reproduce: Whenever user selects payment option as XYZ bank credit card, application crashes.
#3. Understand that bug is a project matter and not personal
Should not beShould be
Title: Application not working properlyTitle: Application does not respond when user selects a specific inventory to be added in cart.
Steps to Reproduce: As I had already conveyed to you and showed you that Application is not working for many pages and shows error pages. Please resolve this issue ASAP.Steps to Reproduce: When user selects a specific part to add it in shopping cart, application does not respond. 
This issue is a barrier in testing the application flow. Please consider it as highest priority.
#4. One bug, one issue only:
Should not beShould be
Title: Certain parts are not select able and application crashes if selected some other partsTitle 1: On Car Accessories page, certain parts are not select able
Steps to Reproduce: On Car Accessories page, following parts are not select able :
Mobile holder
Car backseat pockets
car perfumes
Steps to Reproduce: On Car Accessories page, some of the parts are not select able. Also, when user selects grey seat covers or rich brown seat covers, application crashes.Title 2: On selecting specific types of seat covers on Car Accessories page, application crashes
Steps to Reproduce: On Car Accessories page, when selected following parts, application crashed :
Grey Seat covers
Rich brown seat covers
#5. Provide possible reason, if you know:
Should not beShould be
Title: After cancelling purchase for any accessory from cart, if selected once again, price to be paid shows double of the original priceTitle: After cancelling purchase for any accessory from cart, if selected once again, price to be paid shows double of the original price
Steps to Reproduce: On Car Accessories page, select any item and add it to the cart. Now delete it from the cart and re-select it and add it to cart.Steps to Reproduce: On Car Accessories page, select any item and add it to the cart. Now delete it from the cart and re-select it and add it to cart.

Note: While looking in to database, I found that when user deletes any item from cart, the specific entry does not get deleted from database and therefore when user selects same item again, the price shows up as double. This can be the possible reason of the issue.

Saturday, July 11, 2015

Size Matters: Balancing Line Length And Font Size In Responsive Web Design

As we refine our methods of responsive web design, we’ve increasingly focused on measure (another word for “line length”) and its relationship to how people read.

The popularization of the “ideal measure” has led to advice such as “Increase font size for large screens and reduce font size for small screens.” While a good measure does improve the reading experience, it’s only one rule for good typography. Another rule is to maintain a comfortable font size.

How People Read

People read online text to serve their own needs: to find the information they seek, to discover new ideas and to confirm their notions about life.


In 2006, the Nielsen Norman group released images of heat maps from eye-tracking studies. The areas where people looked at the most while reading are red, areas with fewer views are yellow, and the least-viewed areas are blue. As you can see below, the red and yellow areas form three variations of an F-shaped pattern. These variations aren’t surprising because people read in three different ways.
People read casually, skimming over text, reading words and sentences here and there to get a sense of the content. The heat map below shows the eye movements of someone casually reading about a product. The reader spent time looking at the image of the product, reading the first couple of sentences, then scanning through the bulleted list.
The Nielsen Norman Group explored the F-shaped pattern for casual reading in 2006. (View large version)
People also scan with purpose, jumping from section to section, looking for a particular piece of information. They might only read a word or the first couple of characters of a word as they scan the screen. The heat map below shows the eye movements of someone scanning the results of a Google search with purpose. The person read the first two results more slowly. Then, their eyes jumped from section to section, looking for the search term. Therefore, we do not see a strong vertical stroke along the left edge of the text.
The Nielsen Norman Group explored the F-shaped pattern for purposeful scanning in 2006. (View large version)
Finally, people read in an engaged manner. When they find an article or blog post they are interested in, they will slow down and read the whole text, perhaps even going into a trance-like state. The heat map below shows the eye movements of a person reading in an engaged manner. The tone is more continuous. There is more red (meaning more time spent reading) and less jumping around the page. When the intensity of reading dwindled because they lost interest (the corporate “About us” page might not have aligned with their interests), their eyes continued along the left edge of the text.
The Nielsen Norman Group explored the F-shaped pattern for reading in an engaged manner in 2006. (View large version)


We know that people read in three different ways, but let’s look more closely at how people read — how the F-shaped patterns are formed.

We know that people. Don’t. Read. Each. Individual. Word. Instead, they use their foveal (or central) vision to focus on a word, while using their peripheral vision to find the next spot on which to focus.

People don’t read each word individually.
People use their foveal (central) and peripheral vision to read.

We also know that people don’t fixate on every word, but tend to skip words (their eyes take little leaps, called “saccades”) and fill in the rest. This is especially true of those who read casually or scan with purpose.

People skip words and fill in the rest.
Finally, we know that readers anticipate the next line while moving their eyes horizontally along a line; so, their eyes are drawn down the left edge of the text. This constant struggle between horizontal and vertical motion contributes to the F-shaped reading patterns.
The constant struggle between horizontal and vertical eye movement results in the F-shaped patterns

Line Length (Measure) And Reading

Typographers have been writing about the relationship between horizontal and vertical eye motion for almost a century. In 1928, Jan Tschichold dismissed centered text and advocated for left-aligned text. He argued that this would assist readers by providing a consistent left (vertical) edge for the eye to return to after finishing each (horizontal) line.


We have multiple “rules” for facilitating a horizontal reading motion, one of which is to set text at a reasonable measure. As James Craig wrote in his book Designing With Type (originally published in 1971, now it its fifth edition):
Reading a long line of type causes fatigue: the reader must move his head at the end of each line and search for the beginning of the next line.… Too short a line breaks up words or phrases that are generally read as a unit.
If a casual reader gets tired of reading a long horizontal line, then they’re more likely to skim the left edge of the text. If an engaged reader gets tired of reading a long horizontal line, then they’re more likely to accidentally read the same line of text twice (a phenomenon known as “doubling”).
65 characters (2.5 times the Roman alphabet) is often referred to as the perfect measure. Derived from this number is the ideal range that all designers should strive for: 45 to 75 characters (including spaces and punctuation) per line for print. Many web designers (including me) apply that rule directly to the web. I’ve found, however, that we can reliably broaden the range to 45 to 85 characters (including spaces and punctuation) per line for web pages.


Web designers have started to embrace a reasonable measure for text. Resources abound. Early writings include Mark Boulton’s more poetic approach to typography, which he refers to as “knowing your hanging punctuation from your em-dash” (“Five Simple Steps to Better Typography”). Later writings include Harry Roberts’ more technical approach to typography (“Technical Web Typography: Guidelines and Techniques”).
The most recent (and, dare I say, exciting) development in measure? Its role in responsive web design. More designers are using line length to help determine break points in a responsive structure! Chris Coyer recently developed his bookmarklet to test line length in order to help responsive web designers keep an eye on their measure (“Bookmarklet to Colorize Text Between 45 and 75 Characters”).
But a good measure is only one rule for setting readable text.

Font Size And Reading

A good, comfortable font size is also necessary for setting readable text. This rule is old news. But given the number of responsive websites out there that make text too small or too big in order to achieve an ideal measure, the rule bears repeating.


One benefit of a responsive web structure is readable text — text that people on hand-held devices don’t have to pinch and zoom to read. If a structure is static (like the two-column page shown below), then an ideal measure won’t do the trick. The text will simply be way too tiny to read on a small device such as a phone.
Left: The main column has a good measure (45 to 85 characters are highlighted in yellow). But without a responsive structure, the text is too small to read on a small device without pinching and zooming. Right: The font size (13-pixel Verdana for the left column, 18-pixel Georgia for the introduction and 16-pixel Georgia for the article) is comfortable to read on a laptop.


When designing a responsive website, start with a comfortable font size and an ideal measure to help determine break points. But when the time comes (as it always does), let the ideal measure go.
Text already looks smaller on hand-held devices than on larger devices. This is fine because people tend to hold small devices closer when reading. Current popular wisdom is to preserve the measure by further reducing the font sizes for held-held devices. In practice, retaining a comfortable font size as much as possible better preserves readability. The result will be a less-than-ideal measure but a more comfortable reading experience.
A responsive structure won’t help if small text on a hand-held device encourages readers to pinch and zoom!
Left: To retain an ideal measure, the font size is reduced to 12-pixel Verdana and 14-pixel Georgia for hand-held devices. The text is harder to read. Right: The font size is 13-pixel Verdana and 17-pixel Georgia for hand-held devices. The measure is no longer ideal, but the text is easier to read.


When designing a responsive website, remember that measure and font size affect not only people using hand-held devices. The majority of people still use larger devices, such as laptops and desktop computers.
Some simple responsive structures keep text in a single column that expands and contracts with the size of the device. This can be an elegant, appropriate solution — except when the font size (instead of the column’s width) is used to preserve the ideal measure.
We’ve learned not to set text too small, but text that’s too big also poses a problem. When type gets too big, the reader’s eyes try to follow their usual pattern. But a font size that’s too large takes up more horizontal space, and it interferes with the horizontal flow that readers have established using their foveal vision and their pattern of skipping words.
We’re used to setting online text larger than printed text. This is fine because people tend to place large devices on their lap or on a desk while reading. But overly large text forces the reader to slow down and adjust how far they skip ahead as they read. Reading horizontally becomes cumbersome, and the reader will start to skip vertically down the left edge of the text.
When type gets too big, the reader tries to follow their usual horizontal rhythm. This forces them to read parts of words instead of entire words and to slow down and adjust their reading pattern.

Current popular advice is to preserve the measure by increasing the font size for large devices. For example, the one-column structure below has an ideal measure. But to achieve this ideal measure on large devices, we’ve had to set the text to 19-pixel Verdana, 22-pixel Georgia for the article, and a whopping 26-pixel Georgia for the introduction!
In the layout above, details show the text at 100% size. The text on this web page is way too big for comfortable reading! Simple one-column responsive structures should use a narrower column on large devices, keeping the font size smaller and easier to read. (View large version)
In practice, retaining a comfortable font size as much as possible and simply narrowing the column’s width instead are better. Look at what happens to A List Apart when it’s viewed on a hand-held device and on a laptop.
A List Apart is perfectly readable on a hand-held device. But on a laptop, the text gets too big to be comfortably read. A shorter measure and a smaller font size would help people follow their usual horizontal rhythm. (View large version)

Bonus Section: Line Height And Reading

So far, our focus has been on the relationship between font size and measure in responsive web structures. But line height also affects how people read.


Because readers scan content both horizontally and vertically, lines of text should feel like horizontal lines, not like woven fabric.
A line height that is too tight could undermine horizontal eye movement and encourage scanning down the left edge. It could also force people to reread lines of text. On the other hand, a line height that is too loose could make lines of text visually “float away” from each other. The lines will no longer feel like a cohesive unit, and vertical scanning becomes more difficult.
While there is no perfect line height, a good rule of thumb is to set it at approximately 150% of the font size.
While there is no perfect line height, a good rule of thumb is to set it at approximately 150% of the font size.
Top: When the line height is too tight, it undermines the horizontal reading flow and increases doubling. Bottom: When the line height is too loose, lines of text visually float away from each other.


Setting line height is a complex balance of variables (font family, measure, font size, language). The most important variable when creating a responsive web structure is — surprise! — font size.
Smaller type tends to need more line height, not less. A generous line height helps the eye to recognize small word shapes more easily, and it encourages horizontal motion when the eye gets tired of reading small text.
Left: A line height set at 150% is a bit too tight on an iPhone. Right: The exact same text with a slightly looser line height promotes horizontal movement and helps the reader to recognize word shapes.

Look Closely, Break Rules

When we design a responsive structure, testing it on a large device is easy; we can change a desktop browser’s size quickly. But designing on a desktop or laptop browser means that we are spending most of our time at an arm’s length from the text, and we don’t spend much time seeing how the text renders on small devices.
If you’re using measure to find break points in your responsive website, then you probably care about type and reading. Keep using measure! It’s a great starting point. But to see whether your type truly works, spend some time looking at it closely, on a smaller device. Balance measure, line height and font size as needed.
Remember that all rules are meant to be broken. Heck, Jan Tschichold broke his own rule and used centered text for much of his career. When the time comes, sacrifice measure for a comfortable font size. A good font size (not too small) is readable. A good font size (not too big) promotes horizontal eye motion. A good font size with the proper line height will help your readers find what they’re looking for.