Archive for August 2011
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.
Agile testing has to work with the Agile lifecycle and processes adopted by your team. For example, if you adopt the Scrum methodology, that means you will have to conduct your testing within the Sprint cycles. Agile is about incremental development. So small pieces of functionality are delivered during each iteration. The challenge here is to ensure that new functionality does not break existing functionality. The typically shorter iteration duration of Agile methodology makes this more demanding.
Agile teams have typically tried to adopt Test-Driven Development (TDD) as a solution for testing needs. This is a good solution in many respects, but care has to be taken to implement TDD properly. For example, discussions about TDD usually tend to focus on unit test coverage, which is a major subset, but not the only aspect of testing. Automated testing should also cover system-level testing and workflows that cover functionality across multiple modules. 100% code coverage may sometimes be misleading because workflows may require additional tests.