What is Sandwich testing?
BY krithiga.m
4 years ago
comments comment

Sandwich testing is a type of testing that consist of two parts,they are Top-down approach and Bottom-up approach.It combines the advantages of both Bottom-up testing and Top-down testing at a time.Bottom-up testing starts from middle layer and goes upward to the top layer where as Top-down testing starts from middle layer and goes downward. Big-bang approach is followed for the middle layer. From this layer bottom-up approach goes upwards and top-down approach goes downwards.

Advantages of Sandwich Testing

  • Sandwich approach is useful for very large projects having several subprojects.When development follows a spiral model and the modul itself is as large as a system, then one can use sandwich testing.
  • Both Top-down and Bottom-up approach starts at a time as per development schedule. Units are tested and brought together to make a system .Integration is done downwards.
  • It needs more resources and big teams perform both bottom-up and top-down methods of testing at a time or one after the other.

Disadvantages of Sandwich Testing

  • It require very high cost for testing because one part has Top-down approach while another part has bottom-up approach.
  • It cannot be used for smaller system with huge interdependence between different modules.It makes sense when the individual subsystem is as good as complete system.
  • Different skill sets are required for tester at different level as module are separate system handling separate domains like ERP products with modules representing different functional areas.

Hope this article helps you to understand Sandwich testing.



on 30th March 2012 / by webmaster
Here are some basic SEO tests that you can perform on your Drupal/Non-Drupal website. Whenever a change is made in your site, run these tests for better results and for good SEO ranking. All these test cases points out to possible problems in the Drupal/Non-Drupal website. The observations and results of these tests can then be passed on to the web developer for updations. Check if the meta tags and meta descriptions are given and explains what the page is about in the page as well as html code. Check that the page titles are short and informative in page and html code. Check that the headings (h1,h2) are meaningful and exclusive in html code. Check that the images are 'Alt text' in html code. Check if the ' allow and disallow' given in the html code are working in proper way. Check that the Google analytics status is 'yes' in the google analytics module. Check that site information, site name and slogan are unique and accurate. Check the site loading time. Check if the mobile site is indexed by Google. Check through the w3c validator. Check if the site is shared with social media sites. Check if the 'bread crumb' is working fine. Use different free webmaster tools ; for example go to woorank.com/google.com/bing.com/yahoo.com and check the various SEO details. Check that the xml sitemap covers all links of the pages. Check that the custom 'search 404 error page' is created. Check that the page contents effectively communicates the topic of the page's content. Check that the structure of url is simple to understand and conveying the content information easily. Check if the pages not accessible by anonymous users are restricted in robots.txt by using free webmaster tool. Check the performance of the navigation in a website. Check if the anchor text is easy to convey the contents linked . Check if the backlinks are working in properly. Check whether a page has multiple URL. SEO Software Testing Test Cases Leave a reply Your email address will not be published. Required fields are marker *

on 03rd April 2012 / by webmaster
To ensure the security of confidential data in your Drupal site, testing has to be done to determine whether it protects its data and at the same time maintains its functionality. Web applications are always prone to unauthorized access to or modification of sensitive information. The testing done on the applications to remove such anomalies is called security testing. The following are some of the test cases for assuring the security of a Drupal website Authentication Test whether captcha is set to assure that the application keeps unauthorized users from accessing the Drupal site. Test whether the account should be locked after a determined number of failure attempts. Test whether the admin gets alerts or notification when the account is blocked due to failure attempts. Test whether security question is asked while creating an account. Test whether security question is asked for the password recovery. Test when password is encrypted using Secure Socket Layer (SSL) while sending it . Test whether system prints password characters while entering passwords. Test whether the pages can be accessed by copying and pasting the login URL again without entering the password. Test whether the password field support copy operation. Test if password field is reset to blank while moving next/back . Test whether the password is directly passed through the query string/URL without encryption. Test for the access after the session times out. and session time out settings. Test whether the system asks for changing the password periodically. Test whether the data/pages can be downloaded through FTP or any other source without valid authentication. Test whether the secured pages can be accessed through the browser's history.   Access Control Test whether the user can access admin data. Test whether the user should be able to access an unauthorized page by copying and pasting the URL. Test whether clicking the back arrow should redirect a user to the URL of the last users’ login or their last pages visited.   Buffer Overflows Test whether all data input fields must have reasonable field Lengths and specific data types. Test the amount of text limit allowed in free form fields.   Input Validation Test whether the system accepts illegal characters. Test the maximum length in the field. Test the minimum length in the field. Test the data type. Test whether null value is allowed in the field. Test the format in the field.   Cross site Scripting Test whether the generated pages are properly encoded to prevent unintended execution of scripts. Test whether the dynamically generated pages do not contain undesired tags   SQL Injection Test whether some query inserted in user input fields is being executed by the application.   Improper Error Handling Test whether error messages contain only secured information. Test the response time for the error messages.   Session Management Test for session hijacking vulnerability, if your application uses session identifier in the URL.   Insecure Storage Test whether information must be protected using strong encryption methods.   Conclusion Security requirement will change with respect to the external environment. Constant review and attention to the threat environment is necessary for maintaining a Drupal application's security. For more information, check Drupal Security Tips. Drupal Drupal Development Drupal Security Software Testing Test Cases Leave a reply Your email address will not be published. Required fields are marker *

on 30th May 2012 / by anju.r
A software bug is defined as an error or failure or fault in a system or computer program that produces an unexpected or incorrect result. This is applicable for any Drupal/non-Drupal website. The bug life cycle in a Drupal website consists of steps from identification to closure of a bug. Different stages of Bug Life Cycle are: New Opened Assigned Rejected Test Reassigned Closed Reopened Deferred New: When a tester posts a bug its status is New.Opened: New bug yet to be approved. So when the test leader approves it, its status changes to open.Assigned: When the test lead assign the bug to the corresponding developer , its status changes to Assigned.Rejected: Sometimes the developer feel that the bug is not genuine. So the developer rejects the bug and then the status of the bug becomes Rejected.Test: When the developer fixes the bug and sends it for testing, the status of the bug changes to Testing.Reassigned: If the tester found that the bug still exists or partially fixed, he send it back to the developer. Then the status of the bug is Reassigned.Closed: Once the bug is verified and assured that the bug no longer exists, its status changes to Closed.Reopened: If the issue still comes again, the tester change the status of the bug to reopened and the bug has to go all the above phases again.Deferred: If the bug is decided to be fix in the next version, the status of the bug is changes to Deferred. Drupal Software Testing Leave a reply Your email address will not be published. Required fields are marker *
Leave a reply
Your email address will not be published. Required fields are marker *

Filtered HTML

  • Web page addresses and email addresses turn into links automatically.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
The content of this field is kept private and will not be shown publicly.
CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.