Test Cases
more_horiz
close

on 20th August 2015 / by tiju.thomas
User Interface testing comes under Non Functional Testing type. In UI testing, our intention is to validate user interface which is designed professionally or not. Here is the basic check list for UI testing : Check whether all the required elements are showing correctly in the web page Check whether the contents are displaying correctly in the web page. Check whether the spelling of the objects are correct. Check whether the contents available in the page is aligned properly. Check whether the fonts (font size & type) used in the content region maintains consistency. Check whether the mandatory fields are highlighting correctly. Check whether the colors used in the hyperlinks maintaining consistency. Check whether the background color used in the site maintains consistency or not. Check whether the images used in the pages are properly aligned. Check whether the navigation of the links in the pages are working correctly. Check whether the instructions/ error messages are showing correctly in the screen. Check whether the site conveys a clear sense to its intended audience Check whether the site is consistent and have clearly recognizable look & feel Hey, want to know more about other test cases like this, click here. Don't hesitate to connect with us for any test support. Test Cases Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 19th August 2015 / by anoop.v
The main dispassionate of usability testing is to ensure that the App having the features of intuitive, industry accepted interface and easy to use. Following are the some usability test cases. Ensure that the buttons have the minimum size and be suitable for fingers. To avoid the confusion to the end users place the button to the same section of the screen. Ensure that the apps have consistent and natural icons. Ensure the color of the buttons which have same function in different locations. Ensure the zoom-in and zoom-out facilities. Ensure that contextual menus are not encumbered. Ensure that the texts are kept in Simple, Clear and Visible to users. Ensure that the paragraphs and sentences are readable. Ensure the closing and opening of applications in different stages. Ensure the language conversion is working fine or not. Ensure the synchronization according to user actions. Hope this is helpful, now checkout other test cases and feel free to clear your doubts here. Thank you. Test Cases Leave a reply Your email address will not be published. Required fields are marker *
close

on 20th May 2015 / by krithiga.m
Suppose you have Drupal website where user can purchase product through online. The site allows two types of users such as Registered user and guest user.The site consist of Checkout Process so that customer can enter address details, card details in order to reach the product by hand. Some of the test case against Checkout Page is given below:- Ensure that user can access the Checkout Page only after adding the product into the cart Ensure that Checkout Address Page consist of all the details of product such as Name, Quantity, Amount, etc. Ensure that only registered users are allowed to access the Checkout Address Page. Ensure that Name, Street Address, City, State, Country, Postal code are mandatory field in the Checkout Address page. Ensure that error message is displayed when user enter invalid input in all the mandatory field in the checkout address page. Ensure that Back to cart link is available so that user can modify the cart content if needed. Ensure that user is redirected to Checkout payment page only after entering valid mandatory details in the checkout Address page. Ensure that error message is displayed when user leaves all the mandatory fields in the Checkout Address Page. Ensure that error message is displayed when user leaves any one of the mandatory fields in the checkout Address page. Ensure that Next Button and Cancel Button are available in the Checkout Address Page. Ensure that data's are cleared when user click cancel button after entering the mandatory field. Ensure that Name on Card, Card Number,Expiration date,CWW2 are mandatory fields in the Payment Page Ensure that error message is displayed when user enter invalid input in all the mandatory field in the Payment Page. Ensure that error message is displayed when user leaves any one of the mandatory fields in the Payment Page. Ensure that user is redirected to Drupal website once payment process is completed. Ensure that order number is displayed in the Thank you page of the Drupal site. Hope this article helps you to test Checkout Page. Software Testing Test Cases Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 06th March 2015 / by rajula.s
Email spamming, in simple words misusing the emails of a website is a common concern today. There are many ways by which this malpractice could be prevented. You might be familiar with 'captcha', one of the method used to prevent spamming. (For test cases for captcha refer: http://www.zyxware.com/articles/3308/websoftware-testing-checklists-cap…). Drupal provides some modules like Spambot, Honeypot etc for blocking spam. In this article I have added test cases for ensuring the working of Honeypot and Spambot on a drupal website. Honeypot Ensure that the Honeypot module installation. (by checking the configuration->modules). Make element visible by changing display: none to display: block to make sure that the module works Ensure that on entering values on text field (hidden field) and submitting the form throws an error message. Check the Recent Log Entries to make sure it lists logs blocked during submission. Ensure that the form submitted using valid email addresses (not spam) is successfully getting submitted. Spambot Black listed email addresses used for form submission would be reported as spam (An open site http://www.stopforumspam.com/ provides a list of blacklisted email addresses). Ensure that the added spam is getting reported by checking the recent log messages (/admin/reports/dblog). Since spamming is a major concern to the security aspects of a website, it is always advisable to install these modules on websites. Hope this article helps. Feel free to add your thoughts or more cases if any. Drupal Test Cases Spam Prevention Leave a reply Your email address will not be published. Required fields are marker *
close

on 11th February 2015 / by anju.r
Suppose your Drupal website has the facility to allow user to register in your site. In most of the cases User's e-mail address and username will be unique. In this article will be explaining the cases to be noted for the user registration process. If the site supports user registration, the process may normally happen in two ways. Registration process will be carrying out in the website through create new account process. Through Admin menu bar, People » Add user. Also for registration there may two cases. Admin approval required to login to the site after registration. Admin approval not required to login after registration. Let us check the cases to be tested for registration process in a Drupal 7 website. Admin approval is not required to login to the site Ensure that anonymous user is able to register into the site. Ensure that proper validation is enabled for the fields. Ensure that user is redirected to home page after registration. Ensure that user receives an mail regarding registration. Ensure that user has the proper permissions in the site. Ensure that no admin menu-bars are displayed in the site for non-admin users. Ensure that admin can add user through People » Add user menu-bar. Ensure that there exists no design issues and padding issues in the mail. Ensure that there exists no design issues and padding issues in the registration form. Admin Approval is required to login to the site after registration Ensure that user gets appropriate message after registration if admin approval is required for the registration process. Ensure that user receives email regarding the registration. Ensure that after admin approval user receives an email with login credentials. Ensure that user is able to login to the site using the credentials received through email. Ensure that user is able to change the password. Please note that the menu-bar People » Add user is displayed in Drupal 7. In Drupal 6, it is displayed as user » Add user. Software Testing Test Cases Leave a reply Your email address will not be published. Required fields are marker *
close

on 06th February 2015 / by tiju.thomas
As test case is the important document for testing, testers use different effective techniques for preparing the same. Equivalence Partitioning or equivalence classes is one of the effective techniques among them. It is a black box testing technique, which focusses mainly on the functionality of a software. Therefore the main aim of equivalence partitioning is to prepare an effective test case which covers the total functionality of an application. In this article, I have included a brief note on Equivalence Partitioning. Equivalence Partitioning is a software testing technique that allows the tester to divide the input domain into different partitions of classes, i.e. divides the inputs as valid and invalid classes. It uncovers the classes of errors. For example; Consider if the Input Domain for a Text Field in a site is 1 to 1000. So while preparing test cases there is no use for writing number of test cases for all valid input datas and other test cases for invalid datas. By applying 'Equivalence Partitioning' the testers will divide this Input Domain into 3 classes of inputs : Any value less than 1 ( Invalid ) Any value within 1 to 1000 ( Valid ) Any value greater than 1000 ( Invalid ) Any value within each class of inputs satisfies a particular test case, it is assumed that all the values within those classes will satisfy the test case. The advantage of 'Equivalence Partitioning' is, it allows the testers to reduce the number of test cases, also it reduces the testing time of a software because of lesser number of test cases. If you have additional points, use the below comment box. Happy testing.. Software Testing Test Cases Leave a reply Your email address will not be published. Required fields are marker *
close

on 06th January 2015 / by renjith
A test case is a step by step procedure to test the functionality and design of a software. Test cases are prepared after reviewing the documents required for developing the software. All the requirements should be thoroughly and comprehensively studied before designing the test cases. A good test case should include all the requirements and cover the complete functionality of the software. The software will be tested by executing the prepared test cases. For preparing the right test case, a tester should consider the following factors: Positive Negative User Interface Usability Performance Security Reliability Compatibility Positive: Testing the software in the positive way, that is to check whether the system is functioning properly with correct inputs. For example, testing an number field with integers. Negative: Testing the software in a negative way, that is to check whether the system fails on giving wrong inputs. For example, testing a number field with alphabets, special characters etc. User Interface: Testing the user interaction with the system. For example testing the links, images, alignment, padding, font, colour, labels, navigation, button etc Usability : Testing the efficiency and accuracy of the software, that is to determine whether the user is able to perform the specified task. Successful login/registration to a site by a user is a perfect example. Performance: Testing the performance of the system under a particular workload. Load and stress testing is an example for performance testing ie, testing a system by running multiple applications, testing with maximum number of users etc Security: Testing the security of the system ie, to determine whether the data is protected or not. For example logged out users, by copy pasting the URL or by any other method, should not be able to access the pages which are accessible only for logged in users. Security testing includes Authentication, Authorization, Confidentiality, Integrity, Non-repudiation Reliability: Testing the consistency of the system, that is to determine whether the system is functioning properly in all conditions repeatedly. For example, the system will produce the same result on doing the repeated action. Compatibility: Testing the compatibility of the system on different environments that is to ensure the functioning of the system on different browsers, hardware and operating system platforms. For example testing the product in different platforms like Windows, Linux, Mac etc and on different browsers like Mozilla Firefox, Chrome, Safari, IE etc. Software Testing Test Cases Quality Software Quality Leave a reply Your email address will not be published. Required fields are marker *
more_horiz
close

on 05th January 2015 / by rajula.s
Navigation Menu bar are intended for helping users navigate through important pages of the website. The navigation menu bar can be customized in different ways. Mega menu is one such customized menu bar, which has got high usability factors compared to traditional navigation menu bars. The main advantage of mega menu is that user can view all options in one area, without scrolling down the content. The user can access the mega menu with just a click or mouse hover thereby saving his/her time. Following are the test cases / check-lists for mega menu: Ensure that on clicking the down arrow or mouse hovering the menu item, displays the mega panel. Ensure that the contents on the mega panel is not congested and properly displayed. Ensure that when contents under a menu item is small, the area of the mega panel is getting adjusted accordingly. Ensure that links to read more are given if there is more content to be displayed. Ensure that read more buttons/links on the mega panel directs the user to its corresponding details page. Ensure that the images on the mega panel are getting loaded and getting displayed without cropping. Ensure the alignment, and spacing among the contents. Ensure the positioning of the mega panel. The mega panel should be centre aligned. Ensure the loading time for the mega menu. Ensure the user friendliness of the mega menu. Ensure the browser compatibility of the mega menu. Ensure that the mega menu is responsive on different mobile applications. The mega menu is best opted for commercial websites where different products are categorized. Hope this article helps. Feel free to add your comments. Drupal Test Cases Leave a reply Your email address will not be published. Required fields are marker *
close

on 22nd December 2014 / by rajula.s
Test cases and Test Scenario are the documents used by the testers to ensure that the application meets the customer requirements. These are the most important documents that the testers prepare prior to testing. Even though the core objective of the documents is the same, there is a difference in their representation. Read on to know more. Test cases: Test cases refer to the detailed steps/conditions to be executed to ensure whether the application is functioning properly or not. The test case includes test input, procedure, expected result, and actual result of the functionality to be tested. The test cases can either be positive test cases or negative test cases. For example, if you are testing a search box, one of the positive test cases could be testing whether the search box accepts the valid data (alphabets). The negative test case could be submitting the box without entering any data. An effective test case should cover all the possible cases (that is both negative as well as positive). Therefore, in simple words, a test case is used to ascertain the test coverage of an application. Test Scenarios: Test scenario is a combination of test cases which defines what is to be tested on an application/feature, or simply test scenarios are the series of test cases. Suppose you are testing a login form. Then, the test scenario would simply be a single sentence i.e "Ensure the working of login form". Test scenarios mainly focus on the functionality and not the input datas.This document includes test conditions, where as test cases are the step by step procedure to be followed to meet this condition. Test cases should be written after considering all the requirements. By doing so, the testing process will become simpler yet effective. Hope this article helps. Happy Testing ! Software Testing Test Cases Test Scenario Leave a reply Your email address will not be published. Required fields are marker *
close

on 07th June 2013 / by rajula.s
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: Ensure that the total number of users are same as on the old site from where it was migrated. Ensure that all user details fields such as Name, Email address, Location, Contact details etc are migrated. Ensure that the details migrated are correct. Ensure that the details migrated are not interchanged for another. Ensure that the location are mapped properly. Ensure that the profile pictures are loaded properly without cropped/compressed. These are the basic test cases that I have executed for my project. If you have more points, please add those via the below comment box. Thank You! Software Testing Test Cases Web Testing Quality user migration Leave a reply Your email address will not be published. Required fields are marker *