Software Testing

In a Drupal site, user roles and permissions are an important way of controlling access to the site. This is more so important when there are multiple individuals besides the website owner who administers the site. Other people can be assigned certain 'roles' which define the kind of access that is to be granted. Basically in Drupal, the Site maintainer and Administrator roles are given all the available permissions and Drupal Administrator role receives all permissions throughout the lifespan of the site. This is not the case for other 'roles', where access within admin permissions and time limits only are granted to users linked to those roles.

A major advantage of adding permissions is that, when a new feature is added to a Drupal domain which is not allowed for everyone by default, this functionality can be made specific for a 'role' or a group of 'roles' but granting access to them alone. Roles are not just a way to group permissions, but they also hide important information about the site as well. For this reason, users, roles and their permissions are imperative and have to be set up and configured appropriately and tested systematically. The major Test cases/checklists to be considered while testing roles and permissions in Drupal are documented here.

A contact form is included with websites mainly with an intention to allow users to communicate with the site administrator, sharing their feedback/messages regarding the website or reaching out to the business owner of the site for services / support. In this article I have covered a set of test cases that can be used to test the Drupal site contact form.

You might ponder as to why test a link, or even include it as a test case when there are several other major functionalities to be tested in a Drupal site. Every site, be it Drupal or non-Drupal, contains numerous links, some of which lead to external sites and some that whirl within the site. The 'web' works extensively through links, and it is through links that sites are navigated to and get found. Links are also the underlying indicators for security of a site. So links should be paid attention to and be tested thoroughly. Here are some test cases to help you get started:

If you are a web tester new to a Drupal website and you got a Drupal website for testing, then you can take your baby steps in testing with the basic content types of the site - such as pages, story as almost all sites have at least one content of this type. Read on to know the details about some of the content types in a Drupal website and its test cases.

Automation is the process of evaluating the AUT(Application under Test) against the specification with the help of a tool. In this article we are gong to discuss the Scope of automation in testing.

An XML sitemap or simply sitemap is an XML file containing the URL's of a website. Sitemaps are important tools in letting search engines know of all content present on a site. This is more so in cases where search engines are not crawling the site well because of improper linkage or low significance. There is a module called XMLSitemap in Drupal that allows a site owner to easily set up a sitemap on a Drupal website.

Google Analytics is a service offered by google which is mainly used to analyze the traffic of drupal/non drupal websites. This module gives statistical information such as

Error guessing is a testing technique based on guessing. It is not just guessing, but the skill of a tester. The tester acquires this skill from his prior experience in testing. This technique has got important significance in testing, and is discussed below.

HTML validation is done mainly to ensure that webpages follow the HTML standards and rules set by W3C (World Wide Web Consortium). A webpage with correct HTML helps

File upload fields are one of the most vulnerable elements in a Drupal form, highly prone to hack attempts. So these have to undergo thorough rounds of testing to make sure the data that goes in is perfectly safe.

The criteria required to 'stop testing' is determined by many factors. When a test plan is created it is critical to define the exit criteria. Following are some of the decisions we take to explicitly stop testing during the testing phase.

Suppose we have a Drupal website which uses Ubercart module and Ubercart recurring fees functionality for handling payments and the website has two subscription products one which renews on a monthly basis and another which renews annually. We have to ensure that these two products will be renewed when the next billing date occurs. The following test cases will help you test this.

There is a good chance that most Drupal websites are linked to social networking sites like Twitter and Facebook. In such a scenario we need to verify that the content generated in the Drupal website and passed as feeds to these sites are correctly displayed there. If you are facing the same scenario in your Drupal website and want to know how to test your Drupal website's content feed in social networking sites like Twitter and Facebook then read on

'Completely Automated Public Turing Test to tell computers and humans apart' or simply 'CAPTCHA' is something that we come across in the Log in / contact form of almost every modern website. As the name suggests, it is used to differentiate between humans and computers.

In positive testing our intention is to prove that an application will work on giving valid input data. i.e. testing a system by giving its corresponding valid inputs.

For example:
Consider Drupal webpage containing a textbox whose specified requirement in the SRS document is to accept only numbers. In that case when we perform positive testing, we will give only numbers as input data in the textbox and analyse whether the application is working properly or not. Here, our expectation is that the text box should accept the given input values.

Testing is a very significant phase in the development of Drupal based websites. In this article we are going to discuss how to write test cases for numeric and alphanumeric fields on a Drupal site

Comment Management module helps a site owner to manage the posted comments on his website. Testing a Comment Management module involves a set of test cases and it is always helpful to keep a checklist for this. Here is something to help you out! Following are the test cases / checklists for Drupal 7 default Comment Management Module

Search box helps a user to search data within the website. Following are the test cases / checklists for default Drupal 7 search box

While testing any website, be it Drupal / non-Drupal, one would often have to test Date fields.
Following are the test cases to be considered / checked for, while testing a date field:

QR code is a two dimensional bar code having information which can be recognized and interpreted through electronic signals only. QR code is displayed in square pattern with dark dots in white background.