Knights of Columbus CMS

Knights of Columbus CMS Testing Design

Christopher W Ozoniak 10/27/2010 Submitted in partial fulfillment

of the requirements of

MIT 490 – Senior Projects

Advisor: Dr. Benjamin Bishop Knights of Columbus CMS: Testing Design

TABLE OF CONTENTS

Chapter 1: Introduction______3 1.1 Introduction______3 1.1.a Purpose of the Project______3 1.2 Glossary______3-4 1.3 Document Overview______4-5 Chapter 2: Unit Testing______5 2.1 Definition______5 2.2 Front End Testing______5 2.3 Back End Testing______5-6 Chapter 3: Module Testing______6 3.1 Definition______6 3.2 Front End Testing______6 3.3 Back End Testing______6-7 Chapter 4: Subsystem Testing______7 4.1 Definition______7 Chapter 5: System Testing______7 5.1 Definition______7 5.2 Testing the System______7-8 Chapter 6: Acceptance Testing______8 6.1 Definition______8 6.2 Front End Testing______8-9 6.3 Back End Testing______9 Index______10

1 – Introduction Knights of Columbus CMS: Testing Design

1.1 Introduction

The goal of the Knights of Columbus Content Management System (herein CMS) is to create a Web site that is easily manageable for the Knights of Columbus 5510 Council. It needs to be a Web site that is easily modified by members of the council in addition to the webmaster. It also needs to have a more modern look and feel that will encourage users to be interested in the site. It will require integration with social media to increase traffic flow to the site. It is designed to help others learn more about the Knights of Columbus, and the Knights of

Columbus Council 5510. The Web site will feature various forms of content from the Knights of

Columbus, including pictures and possibly videos. The site will be built using WordPress, a

Content Management System. This Content Management System will allow members of the council to update and create new events, and to update other parts of the Web site. The management of the site will not involve any further coding beyond what is used to create the

CMS. The ultimate creation of the site will be through HTML, PHP, CSS styling and photo editing software such as Gimp or PhotoShop for creating banners and images for the site.

1.2 Glossary

Acceptance Testing is the last step before the system or application is Acceptance completed. It is tested by the end users who will be using the system. This Testing type of testing gives the end users the confidence the system being delivered meets their requirements. An application or program that serves indirectly in support of the front-end Back End services, usually by being closer to the required resource or having the capability to communicate with the required resource. Content CMS- The collection of procedures used to manage work flow in a collaborative Management environment. System (CMS) Cascading Style Sheet – Style sheet language used to describe a website’s visual CSS presentation Knights of Columbus CMS: Testing Design

Module testing is similar to unit testing. It is the idea of testing the smallest Module Testing piece of software or Web site (IEEE 1008).

MySQL Open-source relational database system PHP Hypertext Preprocessor, PHP is an HTML-embedded Web scripting language. Software component that adds specific potential to a larger software Plugins application, in this instance WordPress Subsystem A subsystem test verifies that two or more units of code are interacting Testing correctly to produce the desired result. System Testing tests the system as a whole, rather than the individual pieces. System Testing This test is done from the user point of view. Preloaded CSS themes for WordPress, can be customized Themes Unit testing is a procedure a developer takes during which they test Unit Testing individual software components as they are being developed. The part of a software application that a user sees and interacts with. User Interface Similar to a plugin but it is designed to provide a simple way to arrange the Widgets various elements of your sidebar content A simple and straight-forward user interface used to interact with the system Web-interface and underlying database. This is made of a set of interrelated pages that communicate with each other and the web server. WordPress is a state-of-the-art publishing platform with a focus on aesthetics, web WordPress standards, and usability. WordPress is both free and priceless at the same time.

A free and open source cross-platform web server package, consisting mainly XAMPP of the Apache HTTP Server and MySQL database.

1.3 Document Overview

This document will demonstrate the various ways testing is performed throughout the development process of the Knights of Columbus CMS. The testing is divided into five different sections: unit testing, module testing, subsystem testing, system testing, and acceptance testing. Each section will explain what the specific test is, how it is done, and how it is related to the Knights of Columbus CMS.

2- Unit Testing Knights of Columbus CMS: Testing Design

2.1 Definition

Unit testing is a procedure a developer takes during which they test individual software components as they are being developed. With the Knights of Columbus Web site being created through a CMS, like WordPress, the backend has already been tested and checked for inconsistencies. The database is created in the initial setup of the CMS by creating a table in the Front End of the database (in this case MySQL).

2.2 Front End Testing

Unit testing on the Front End of the Web site is the most important factor for testing.

The Web site the user sees requires everything to be checked for proper function. If a problem arises it could be from various sources, such as an issue with the CSS, HTML, JavaScript or a plugin. This means the pages must be checked for consistency and must be free of quality issues. If the pages are checked on a consistent basis they become considerably easier to repair when issues arise. If the site is checked routinely, fixes should be relatively simple.

2.3 Back End Testing

Back End testing is how the user interface (herein UI) interacts with the database structure. It is built into WordPress through the Administrator panel. It controls all of the pages, categories, tags and other necessities of the Web site. These are in the form of tables within the database. Some of these tables are wp_users, wp_posts and wp_comments. These tables set the Back End for what appears on the Front End of the site.

3- Module Testing Knights of Columbus CMS: Testing Design

3.1 Definition

Module testing is similar to unit testing. It is the idea of testing the smallest piece of software or Web site (IEEE 1008). Any unit of the site is tested and compared with unit specifications. Each module in the Knights of Columbus CMs is thoroughly tested for issues like browser compatibility.

Module testing on the Front End occurs through the user of an internet browser. For the Knights of Columbus the browsers the system will be tested on are Microsoft Internet

Explorer, which contains about 46.45% of all users (as of September 2010) Mozilla Firefox

(29.33%), Chrome (9%), Safari (5.49%), and mobile browsers which make up about 4.5% of internet browsers. If issues arise, the CSS must be modified to work with the different display of the Web site an internet browser may have.

Module testing on the Back End occurs when the content is checked to make sure it is within the correct module. WordPress automatically displays content in certain forms based on how the chosen module. In this case, content will be arranged differently on the Back End as compared to the Front End. The Back End of this CMS has a large influence upon the Front End, and thorough testing must be done for each. If something in the Back End influences the Front

End, and seems to be incorrect, work on the CSS and the other parts will need to occur.

4- Subsystem Testing Knights of Columbus CMS: Testing Design

4.1 Definition

A subsystem test verifies that two or more units of code are interacting correctly to produce the desired result. In this case since the Knights of Columbus site is hosting on an outside server, this is unnecessary.

5- System Testing

5.1 Definition

System Testing tests the system as a whole, rather than the individual pieces. This test is done from the user point of view. In this case, we would test that each page works individually and together, the navigation is correct, all the links work correctly, and all plugins are configured and working correctly. Systems tests should be configured so that users with less of a technical background are able to complete it.

5.2 Testing the System

In order to complete a system test, there must be some form of content within the Web site. The content that is entered to the site should be related to the respective page it will be displayed on. When testing for the photos page occurs, the Lightbox 2 application should be displayed correctly and a “Close” X button should close the Lightbox 2 window that has appeared. We must also test the other functions and plugins that have been installed into the

CMS. In this case, there is the Calendar plugin. Under the events page we should find a calendar, we should make sure all the events display correctly. This calendar along with all the other plugins and CSS should be tested for cross-browser compatibility. Knights of Columbus CMS: Testing Design

6- Acceptance Testing

6.1 Definition

Acceptance Testing is the last step before the system or application is completed. It is tested by the end users who will be using the system. This type of testing gives the end users the confidence the system being delivered meets their requirements. For the Knights of

Columbus CMS, this process first began when the need for a more modern site became apparent. The members of the council listed their needs and it is an ongoing process. When the council ultimately decides on a finished product that fits their needs, the acceptance testing will be complete.

The Front End testing of the Knights of Columbus is accepting the finished design of the

Web site. The layout of the site must be fully complete and functional. It must meet all the specifications and requirements that the council agreed to so that the Web site can be finished.

Everything about the site must be accepted, from the CSS to the WordPress template and design. If it is not approved then the council must reconvene and go over what needs to be changed.

If the Knights of Columbus Council 5510 decided that the Web site is suitable then the

Back End will be accepted as well. Since WordPress creates and manages most of the Back End on its own, the only things left are the page titles, categories and tags. If there is an issue in this Knights of Columbus CMS: Testing Design area, it will be simple to correct within the control panel of the CMS. There are no current plans for Beta testing, other than the official first release. Feedback is planned to be accepted for the site’s initial release both from the members of the council and from the public who use the site as well. The feedback will be used to make any necessary changes to the Web site.

Acceptance Testing, 2, 3, 8 Apache Tomcat, 4 Back End, 2, 3, 5, 6, 9 CMS, 3, 4, 5, 7, 8, 9 CSS, 3, 4, 5, 6, 7, 8 Module Testing, 2, 4, 6 MySQL, 4, 5 PHP, 3, 4 Plugins, 4 Subsystem Testing, 2, 4, 7 System Testing, 2, 4, 7 Themes, 4 Unit Testing, 2, 4, 5 User Interface, 4 Widgets, 4 Knights of Columbus CMS: Testing Design

WordPress, 3, 4, 5, 6, 8, 9 XAMPP, 4