Drupal

Suppose your drupal projects contains products to sell. And you can use coupon code while purchasing products. For using coupon code in your druapl site, Ubercart Coupon code module may be installed. Please check the below cases which contains the test cases of checking coupon code functionality.

Suppose your Drupal project handles products which can be purchased through online and you are using Ubercart 'taxes' module to handle tax rates which are applicable to your product. Also Admin has the permission to add tax rates and conditions. And a registered user can buy the product. Here I am going to explain some of the test cases which you have to execute while testing this functionality. The cases you have to test are:

If you own/manage an online store using Drupal and Ubercart, you would have encountered situations where you wished to set different prices for different options of a product attribute in ubercart. For example, if your store sells books and you want to add extra price for hardbound editions, here's how you can do it. Read on to know how to set this up in Ubercart

Integration testing is grey box testing method in which combined parts of an application is tested to determine whether all these functions works together. Let us learn this with an example. Suppose your Drupal site sells online products and the shipment charge is set in such a way that it will be applicable to the product depending on the weight and destination. While doing the unit testing, tester has to test product selection, setting price,setting shipment to the destination etc separately. But in integration testing we test all these different functionality as a whole.

The performance of a site should be tested in order to ensure how fast and reliable a site is. In this article I will be covering the steps to be followed for carrying out some of these performance tests. The topics being 'testing the GZipped Content Delivery', 'Whether FTP is enabled on Server', 'MySQL Remote Access on Server' and 'Password Based SSH Access on Server'. Drupal Performance Test - GZipped Content Delivery In order to check the gzipped content delivery,

User migration in web application is the process of migrating all users from one site (development site) to another (live site). Recently I have worked on a project where I got a chance to test user migration. In our project we had developed user migration in a sandbox environment. Following are the test cases for user migration. Test cases/checklists:

Drupal sites usually have authorized as well as unauthorized users. The privilege of authorized users is that they can access certain pages of the website in addition to the pages that can be accessed by unauthorized users. A user account page/Login page is included in Drupal for those users who wish to access the website as an authenticated user. Read on to know the test cases to test the login page in Drupal. The default Drupal Login page mainly consists of following three tabs (Check the images for reference).

When a tester identifies a bug, they need to report it clearly to the developer as soon as possible. Email is a very time consuming tool for such a task. We use Redmine, an open source project tracking tool to report bugs on the software we develop. Read on to know to use Redmine as a bug reporting tool for your Drupal site.

Global Redirect is a functional module which ensures the correct redirection of users to the alias of a given drupal path, thus avoiding duplicated content from multiple URLs. This is very important for SEO because otherwise search engines will see the same content at the Drupal path as well as at its alias causing it to believe that the site is duplicating content at two different URLs

When focusuing on Drupal website development, 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 contact form is included with websites mainly to allow users to communicate with the site administrator, share 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.reach

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 website. 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:

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

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.

A few Drupal users having a multilingual Drupal website had noticed that the Price field disappears when adding a product in another language in a Drupal site running Drupal Commerce. If you are facing the same issue with Drupal Commerce in your Drupal site then read on to know the solution.

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.

You might wish to know how to format a price using PHP which could be useful while theming Ubercart invoices in your Drupal site. Its extremely easy to do that. Read on to find out more.