Go to Pay4Bugs.com

The Pay4Bugs Blog

Pay4Bugs is the original pay per bug software testing marketplace. Our testers seek out and report problems with your software or website before they cause you to lose sales and customers.

Testing a Website - A Suggestion List of Website QA Assignments

Posted by C.S. Hsia on · Comments

Companies sometimes ask us what they can test with Pay4Bugs, to which we respond "anything!". Through the months, our testers have proved that they can test everything from user behavior, broken links, problems in Ruby on Rails, and even fixing grammatical errors.

Today we want to give everyone ideas on how to use Pay4Bugs to improve you product and services, starting with things you can do to test your website. This is information that should be useful for any company with websites that draw significant traffic and generates revenue from the web.

  • Meta Tags - Sometimes what you don't see is more important than what's rendered into a web browser. When Google and other popular search engines crawl the website, they're looking for the proper <meta> tags. If your site doesn't have meta description tags, Google will display the first paragraph of the page in the search results, which are not necessarily descriptive.
  • Unclosed Tags - Modern day browsers are forgiving, to the point sometimes we have sloppy code with unclosed tags that do not show up to the untrained eye. Ensure the highest level of browser compatibility with properly formatted HTML tags.
  • Browser Incompatibility - Developers all wish that everyone was on Firefox, Safari and Chrome, but the reality of the internet is that most people are still on Internet Explorer. Misaligned images, non-functional links, the list goes on. Pay4Bugs has a diverse group of testers to help you with the heavy lifting on cross browser testing.
  • Excess/Unused Code - Sloppy code, excess code, commented out code. Not only do they slow down page loading speeds, they are also viewed as a negative by Google. In the days where we all have too many tracking pixels, some unused pixels might even throw hidden 404 errors.
  • Secure/Unsecure Errors - Users are demanding higher levels of security on the internet, so how do you cater to both secure and insecure visitors? Some browsers are also notorious with throwing security warnings and error messages that spooks a user from your website, even though you might have done nothing wrong.
  • Encoding - We love UTF-8, but we acknowledge that many other encodings exist. How will the functionality of the site handle different system encodings? Only way to find out is through comprehensive testing.
  • Broken Links - When's the last time you actually "reported it to the webmaster" when you encountered a broken link? I'm guessing never. Every broken link seriously damages your professionalism, give the testers an incentive to hunt them down.
  • Grammar Mistakes and Typos - Spell check doesn't see everything, and writers often cannot find their own mistakes. You'd be surprised by what some Pay4Bugs testers can find.

Check back next week as we share some items to test for software applications.

Comments