Drupal Testing
more_horiz
close

on 15th May 2015 / by anju.r
When you test a Drupal website , most of the time you come across the task "Implement Pathauto module" in you website. So before you start testing, you have to build an idea of what is Pathauto module and how you can test it. Pathauto, as its name suggests automatically generates user friendly URLs. Pathauto depends on the core module path, which is used to rename URLs. So please go through the explanation below to understand it more precisely. Pathauto module is implemented for generating friendly URLs for your contents such as nodes, taxonomy terms, users etc. This is generated automatically. This allows you to create URL aliases like /category/your-node-title instead of /node/1. These aliases are based upon a "pattern" system that uses tokens which the administrator can change. The modules enabled are Pathauto and Tokens. Cases to be tested Check whether the url of the content is like /category/your-node-title instead of /node/1 while creating content. How to test this? Click content--> Add content Create any of the content where pathauto module is applied. Check whether the url is created as such as website/node/2. (ie node/2 will be replaced by the pattern) Check the above case for all the contents. Check whether the url displayed is same for all users. Hope this article helps you to test the function more clearly. Happy testing. Drupal Drupal Modules Drupal Testing Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 04th March 2015 / by rajula.s
Waterfall model a process in software development, where all the development phases such as requirement gathering, designing, implementation, verification and maintenance were carried out separately and executed only after the completion of each phase. The major drawback of this model is that, the in between changes from the client cannot be included. Since the working model reaches the client only at the final stage of the development process, there can be chances of misinterpretation of requirements, which consumes more time in fixing. Here comes the advantages of agile model. Agile model Agile model is an iterative and incremental model where all the development processes are carried out simultaneously. Here there is more of interactions than processes. In this model, client can view the so far completed tasks and the changes can be incorporated. One of the agile development model is scrum. Main Features of Agile Models are Agile methodology scrum. In scrum we will have self organising teams. Product is designed, coded, and tested during the sprint. The main aim of scrum is to deliver the highest business value in shortest time. Roles and responsibilities: Product owner He is the Representative of client. He is the one who gathers requirement (define features), prioritizing tasks and managing release dates. Scrum Master Similar to project manager, a srum master is the person who is responsible for assigning the task, monitoring the team, organising meetings. Scrum Team The scrum team may contain 5-9 people including Programmers, testers, designers, business analyst. Sprint: It is a Series of iterations having a Duration 2–4 weeks. In between requirement changes will not be handled on the current sprint. They are moved on to next sprint. A list of all desired work/requirements on the project are Prioritized by the product owner such that the top items on the list are prioritized and included into sprint back log. Daily scrum meeting: Scrum, the daily 15 minutes will be co ordinated by the scrum master. Following 3 questions will be asked during scrum. What did you do yesterday? What will you do today? Is anything on your way? Even though the questions were small and less in number, the answers of these questions will help team members in getting a clear cut picture about the project. Here the meeting will be informal where all the team members are free to raise their concerns about their assigned tasks. Taking into consideration of the above advantages, agile model is now more preferred. Drupal Testing Leave a reply Your email address will not be published. Required fields are marker *
close

on 11th February 2015 / by anoop.v
Cause effect graphing is a mapping technique, which is used to analyse combination of input conditions and effects may be through of as the output. The Cause-Effect Graphing technique derives the least number of test cases to cover 100% of the functional requirements to improve the quality of test coverage.The cause-effect graphing technique uses the same algorithms that are used in hardware logic circuit testing. It has the ability to detect defects that cancel each other out, and the ability to detect defects hidden by other things going right. It is a graphical representation of inputs (causes) with their associated outputs (effects), which can be used to design test cases. Advantages: They are easy to understand and intuitive to use. Transform each column into test case. Systematic method for generating test cases representing combinations of conditions. Visual clues for missing or incorrect relationships. Example: “Sun” is a cause for “heat”. “Fire” is a cause for “heat”. “Sun” is a cause for “sunburn”. So, there are 3 cause-effect relations in this example: (Sun->heat) (Fire->heat) (Sun->sunburn) This is a testing method which is suitable for Drupal programmers as well as testers.It play an very importent role in the field of software testing. Drupal Testing Software Quality Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 16th January 2015 / by anju.r
Suppose your drupal projects contains products to sell. And you can use a coupon code while purchasing some products. For using coupon code in your Drupal site, Ubercart Coupon code module should be installed. Please check the below cases which contains the test cases of checking coupon code validation functionality in Drupal website. Ensure that error message will be displayed for invalid /expired dates. Ensure that error message will be displayed after the maximum redemptions per code. Ensure that error message will be displayed after the maximum redemptions per user. Ensure that error message will be displayed after the maximum redemptions per user. Ensure that error message will be displayed after the Minimum order quantity. Ensure that error message will be displayed for other than the Applicable product classes. Ensure that error message will be displayed for other than the Applicable products. Ensure that error message will be displayed for other than the Applicable SKUs. Ensure that error message will be displayed for coupon code that is used other than the Applicable taxonomy terms. Ensure that error message will be displayed for other than the specified users. Ensure that error message will be displayed for other than the specified user roles. Ensure that error message will be displayed for inactive coupon codes. Thus we can ensure that all the cases should be checked by going through the above steps. Please be note that cases to be tested may vary depending on the requirement. Drupal Drupal Testing Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 16th January 2015 / by anju.r
Suppose you have a Drupal website which supports multilingual sites with translated content and the user has the permission to choose the language. On selecting the language all the contents should be converted to the selected language. This article sheds light on how the testing of this feature comes to be. Read on to know how to test Drupal site with translatable content. If the Drupal site supports multilingual site with translated content, the following modules will be enabled. Core Modules Locale Content Translate Custom Modules i18n(Internalisation) l10n(localization helper modules) Entity Translation Main features that should be tested are Test the data Ensure that multi-lingual web sites store the data in the UTF-8 Unicode encoding format. Ensure that the displayed by the web site should be correct even if the entered data is in the other language. You can test the character encoding for your website in Mozilla: go to View -> Character Encoding. IE: go to View -> Encoding. Test the cultural issues We should check the following informations while testing data as each language might be meant for users from a particular culture. Ensure that colors displayed in the sites are correct. Ensure that the text direction (this can be left to right, right to left or top to bottom) is correct. Ensure that format of salutations and addresses are correct. Ensure that measures are correct. Ensure that currency symbol changed depends on the language. Ensure that date format also changes correctly. Test the other controls in the site. Ensure that the web site provides correct error messages in the other language. Ensure that no junk characters are displayed while translating characters. Testing the labels. Ensure that the translated labels doesn't expand. Ensure that the labels are not truncated. Ensure that the overlay on in all languages. Ensure that there is not any incorrect word wrapping etc. This article specify some of the cases which should be considered while testing multilingual site with translated content in Drupal 7. Procedure may depending on the drupal versions and requirement. Drupal Drupal Testing Leave a reply Your email address will not be published. Required fields are marker *
close

on 04th July 2013 / by anju.r
One of the most important aspects of a Drupal application is obviously its interface which is all what an end user gets to see. These Web Design issues/bugs negatively affect the final look and feel of the end product. Here are some of the most common design issues to be avoided by a Drupal tester. Common design issues in a Drupal site 1. Alignment issues Button alignment issues Buttons should be left/right/central aligned. If there is more than one button on a page (as in the example below) then the alignment opted for both th e buttons should be the same. Text alignment issues Content should be left/right/central aligned.(proper spacing should be given between the title/text and text/button) Button text ("more") should be centrally aligned. Alignment issues to be noted in case of forms which contain text fields and buttons All text fields in a form should be vertically aligned. All text fields should be of equal width. An improper spacing like in the given example takes away the look and feel of the form. All text fields should start and end with the same level. 2. Another serious issue occurs when some of the expected elements/client requirements are missing. Icons or menu bar may be missing (due to the lack of attention) 3. Typos in the content are often ignored New text should begin with capital letter. Proper Spacing should be given after "," ":" etc 4. Overlapping Often the text in the content overlaps with the nearby text/buttons/images. 5. Color differences are another issue which can be easily noted. Color differences of Buttons might occur. Text might occur. 6. Font differences are also a common bug noticed in most of the sites. Issue might be with The Font Family The Font Size The Font Weight 7. Images getting cropped. Often images might get cropped at its left/right/top/bottom. Re-sizing of images to a specified width might compress/stretch the image. 8. Another issue commonly found in a Drupal website is that the node/content may be displayed in the URL By checking all these cases, we can assure that Design issues doesn't exist on your Drupal site. Software Testing Web Testing Drupal Testing Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 01st July 2013 / by rohith.pv
Recently PayPal changed their policies and creating a sandbox account was a bit confusing for me, when I wanted to test my ubercart site. However, I created one and thought of writing about it in case some one needs it. So, here it goes. We can manage a PayPal account as well as sandbox account at the same time. We can create either a personal or business account to create a sandbox account. This article may help you to create a sandbox account to test your PayPal payment methods. Logging-in with PayPal, provides a single, secure solution to verifying identity. You no longer have to remember a second login for the Developer site. Creating a PayPal account Go to PayPal.com an click signup. Create an account with your details. You don't need to enter bank/card details when you want only a test account. Now go to developer.paypal.com and login with you existing PayPal account. To get your test API key Go to Applications » sandbox accounts. Here you can see one account which was created by PayPal. But to create a working sandbox account to test some payment method you need to create business (merchant account). To create a new sandbox account click on "Create Account" in sandbox accounts tab Select account type as Business (merchant account). See the image below. Give email, password and name. You need this details to check your order details. leave PayPal balance as blank. Do not add any amount over there. Next select any credit card type and press create account button Same way you can create a buyer account also. Note that here you have to select Personal (buyer account) option. Once you create a buyer account go to profile then funding, here you can see you card details. You can use these details to test a purchase in your website. To see your API credentials you can go to sandbox accounts » click on you email address » profile » API credentials. This is the API key that we have to save it in our website. If you want to see your buyer card details, go to your buyer account » profile » funding. Once you test your payment with your website, to see your order details in PayPal click on sandbox site link under the merchant account. Here login with your merchant username and password. Click on "All account activity" link. Hope this helps some of you. Drupal Drupal Testing Paypal Leave a reply Your email address will not be published. Required fields are marker * anil babu (not verified) access_time 23 May 2019 - 00:10 To create a new sandbox account in sandbox accounts tab there is no Option for "Create Account" button for me Add new comment
close

on 07th June 2013 / by rajula.s
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). Create new account Login Request new password This article will cover all possible test cases for the above three tabs. Test Cases for Log in: Registered users can access their privileges by entering their Username and Password in the respective fields of the login form. There will be a Captcha field to ensure security. Ensure that the system accepts a valid Username and password combination. Ensure that the system rejects invalid Username and password combination. Ensure that the user is not able to login on entering invalid username and correct password. Ensure that the user is not able to login on entering valid Username and invalid password. Ensure that an error message is displayed on leaving the mandatory fields empty.Drupal default error message for the above case is: Username field is required. Password field is required. Captcha field is required. Ensure that the password is case sensitive. Ensure that the inputs given in password field are automatically converted to a masked/encrypted form. Also ensure that this input entry remains to be in masked/ encrypted form when copy pasted. Ensure that the system accepts the valid Captcha. Ensure that the system rejects invalid Captcha. Ensure that the Captcha code changes as the System reloads. Ensure that the user is redirected to the corresponding page on submitting valid input data in the login fields. Test Cases for 'Create new account:' Creating a new account page allows users to register to a site by entering valid username and e-mail address in the respective fields. Ensure that the system accepts the valid username and e-mail address combination. Ensure that system rejects the invalid username and e-mail address combination. Ensure that the system rejects the valid e-mail address and invalid username combination. Ensure that the system rejects the invalid e-mail address and valid username combination. Ensure that an error message is displayed on leaving the mandatory fields empty.The default Drupal default error message for the above case is: Username field is required. E-mail address field is required. Test Cases for Request new password: The Request new password form allows a user to request for a new password in case if the he forgets the password. On entering the correct username or email, a request for new password will be sent. An automatically generated link will be mailed to the user's mail id. On clicking that link,a user will be directed to his profile edit page where he can enter a new password thus access his existing account. Ensure that the user receives new password on entering his/her username. Ensure that the user receives new password on entering his/her e-mail address. Ensure that an error message is displayed on submitting the form by leaving the fields empty.The Drupal default error message for the above case is: Username or e-mail address field is required. Ensure that an error message "Sorry, 'test' is not recognized as a user name or an e-mail address."is displayed on entering unrecognized user name or e-mail address (here 'test' is the entered data/input). Hope this article helps. Happy Testing! Drupal Software Testing Test Cases Web Testing Drupal Testing Leave a reply Your email address will not be published. Required fields are marker * Anonymous (not verified) access_time 23 May 2019 - 00:10 This is a well written article. Thanks Add new comment
close

on 04th June 2013 / by rajula.s
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. Redmine offers an effective way for issue tracking, since this helps the user to communicate to his team members as well as viewing all related issues in one place. In this article we will see how we can report issues via project issue tracker tool 'Redmine'. A screenshot of report page is attached for further reference. For reporting a new issue follow the steps below: Login to project tracker using your valid username and password. Log in-> (Your)Project -> New issue. Following are the main fields on the report page. Tracker: Select the drop down as Bug. You can see other options like Feature, Task, Support. Since we are reporting a bug, we need to select the option Bug. Subject: This field is nothing but the title of the issue. Include a brief comment of what the bug is. The title should be meaningful such that the developer should be able to make out a rough idea of the issue from this title. Description: This is an important part of the report. The description field is the place where we communicate with the developer on what the bug is all about. The steps to reproduce the bug should be included so that the developer can reproduce the bug by following those steps. We can also include the location of the bug(link of the page where it occurs), the screenshots etc.. can also be attached so that the developer can easily understand the bug. We can also format our text by using the available formats on the description block. Status: The status has got 2 options. New and Feedback. When we are reporting a bug, the 'New' option should be selected (If we need any support/assistance, then it can be assigned as a Feedback). Priority: Depending on severity of the bug, the priority will have to be set. The priority can considered Normal, Low, High, Urgent and Immediate. The order of fixing should be Urgent>Immediate>High>Normal>Low. If you want the bug to be fixed at the earliest, then select the option urgent. Likewise select the priority depending on the requirement. Assignee: Select the respective person to whom you want to assign the task (often the person who developed the feature). Target version: The tasks may be divided into different sets say set1, set2 and so on. This is done for setting targets with an intention to finish that set of task in a given period of time. Here select the target of your bug accordingly (according to the needs of your project). Start Date: Here input the date you are reporting the issue. Files: Here you can attach the files/screenshots by browsing. Make sure that you have entered all mandatory fields and only after that should you submit the Create button. The team members and clients can themselves get updated on the project via the issue tracker. Thus issue tracking plays a vital role in project management. Hope you enjoyed the article. We would love to hear your feedback and views on the latest trends in Software Testing. Please use the comments form below to do that. Drupal Software Testing Redmine Drupal Testing Leave a reply Your email address will not be published. Required fields are marker * Anonymous (not verified) access_time 23 May 2019 - 00:10 Nice article. Thanks Add new comment
close

on 03rd June 2013 / by rajula.s
When a user frequently visits a webpage, the browser automatically saves or in other words caches that particular page. This helps the user to access those pages in future which saves time. However due to caching, the changes made on a site do not reflect at once and its not useful during development or testing of a Drupal site. Therefore it is important that testers clear the cache before they start testing. Caching can be performed by both the site and the browser. Read on to know how to clear the Drupal cache. How to clear site's cache in Drupal The administrator can clear cache in two ways. He/she can just 'Flush all caches' or he/she can access it from the 'Performance' menu. Have a look at the steps below. Log in as administrator. Mouse over the 'admin-menu-icon' (on the menu bar), and click the option "Flush all caches". As a result, a message ('Caches cleared') will be displayed. For clearing the cache from performance tab, follow the steps below: Log in as administrator. Select the option 'Performance' under Site configuration on the menu bar. Click the button 'Clear cached data'. Caching increases the performance of a site. Implementing 'Boost module' can also increase the performance of your site. If you are in search of steps involved in testing Boost caching, you can go through the article - how to test boost caching on a Drupal site. Drupal Software Testing Drupal Testing Leave a reply Your email address will not be published. Required fields are marker *