Posts Tagged ‘software testing company’
Ivesia has a good experience in testing websites in various domains like Media & Entertainment, Dating, and Digital News Media. Though testing of websites requires minimal training and knowledge about application, it requires a tester to possess the skill of testing the site from Business user’s perspective
We consider the following aspects to QA on websites
- How user friendly is the site?
- Testing portion of websites which integrates the websites with network community like facebook, Twitter etc.
- How compatible is the website across various browsers?
- Of course, any Typo or verbiage problem in page content
- Accessing websites from iPhone using user agents or iPhone Simulator
- Verifying Statistics information like – Total Number of Visits, unique visits to site, Traffic observed in websites
Ivesia provides long term QA services for many websites across different domains such as dating website, entertainment Media website, news media websites. Many of these websites are built on the Drupal content management system. Drupal CMS facilitates the publishing, managing and organizing wide variety of content for a website.
These are some of the features that need to be considered when testing in QA for websites built on Drupal platform:
- Drupal offers easy content updating and management capabilities. This means that much of the content displayed on the website will come from end users, rather than the programming staff.
- Drupal gives a precise control over the websites URL structure. Routing URLs may need to be tested.
- Drupal has strong user role and access control functionality. We can create many custom user roles with custom access levels. For a Drupal installation, we need to understand what the custom user roles are and test for them.
Successful testers avoid overemphasis on functional correctness, and focus on the ways in which people might obtain value from a program — or have that value threatened. Being a tester, reporting bugs clearly in order to alert a developer is just as important as verifying functional correctness. Testers should possess good documentation skills in addition to their testing capabilities. There are several instances that I know of where a major bug was improperly documented and reported to the developer.
My post offers a clear example that demonstrates the importance of documenting bugs properly, which is taken from one of our own testing instances. We needed to perform functional testing on a new feature that had been introduced for a media site. After completing functional testing, we were supposed to perform a regression testing on the media site since release was scheduled on the same day.