Testing Instructions
This document has the purpose of evaluating testing skills. It contains instructions to install and test the products we are using.
Questions and comments to: francisco.vives@clarolab.com.
General Information
Company Link: http://www.jivesoftware.com/
Product: Clearspace / Jive Engage
Information about QA: http://www.softwareqatest.com/
Installation instructions
Download and Install Tomcat 6 (stable version)
Download and Install Postgres (stable version)
Download and Install Java 1.6 (http://java.sun.com/ > Download Java SE > JDK 6)
Download the files located in: http://www.clarolab.com/clearspace/index.html
Set your Operating System variable JAVA_HOME to the JDK 6 based directory (for example: c:\Program Files\Java\jdk1.6.0_03\)
Clearspace Basic Setup
Create a postgres database
Copy the file clearspace.war to the tomcat/webapps directory
Copy the file postgresql-8.3-603.jdbc4.jar to tomcat\lib\
Uncompress the file jiveHome.zip in any place (for example: c:\jiveHome)
Startup Tomcat (tomcat\bin\startup)
Fill in the jiveHome directory (for example c:\jiveHome)
Chose Standard Database Connection
Database Settings:
JDBC Driver Class: org.postgresql.Driver
Database URL: jdbc:postgresql://localhost:5432/DATABASE_CREATED
Username: postgres
Password: the one set during the installation
Press Test Connection and then Continue
Default user settings
Skip Document Sharing Setup
Usage Statistics > Continue
Other Settings > Continue
Admin Account Setup > Skip This Step
Stop Tomcat
Start Tomcat
Login the admin console
- URL: http://localhost:8080/clearspace/admin/
- User: admin password: admin
- Create a space
Website URL: http://localhost:8080/clearspace/
It is recommended to create as many users as needed avoiding the usage of the admin user.
Testing Areas
This section contains 4 different areas of testing to be carried out.
A. Perform an exploratory testing on the following areas:
Documents, Blogs and Discussions > View as PDF
Rich Text Editor (New > Document > Chose a space). Use different format and colors to see if the rich text editor is working fine.
User Profile
If you see any error, please report them as explained below at Bug Reporting.
B. Verify the following issues to see if they are still happening or not:
http://www.clarolab.com/clearspace/issues.zip
CS-4021
CS-3053
CS-2393
CS-3579
CS-4041
C. Write Test Cases associated to the Announcement feature.
Login to URL: http://localhost:8080/clearspace/ with admin / admin
Identify the announcement functionality and write test cases about it. Please include positive and negative test cases.
For each test case specify: priority, title, steps / expected results.
D. This exercise is optional: Test openfire – Clearspace connection
Install/Start Clearspace
Create testuser1 and testuser2
Login as testuser1 and create a document
Login as testuser1 and create a discussion
In the admin console, enable real-time options
Download Openfire and Spark from: http://www.igniterealtime.org/downloads/index.jsp
Install and Run Openfire
Once installed, go to the admin console http://localhost:9090/ (admin / admin) to configure Openfire
In the “Profile Settings” step, select Clearspace Integration
Complete the installation
Install and Open Spark
Install Spark
Open Spark
Login as username: testuser1 password: the same than in Clearspace. Server: localhost
Go to Clearspace
Login with any user
Validate if bullet next to testuser1 is in green (user is available)
Capture a screenshot of the Clearspace Main page.
Bug Reporting
If you found any bug or improvement during the testing, they could be reported whether in English or Spanish language. Use the following guideline to report the bugs.
Title: describe the broken functionality.
Description: provide information relating to the issue, error logs, tomcat logs, urls, steps to reproduce the issue, etc.
Acceptance Test: When the issue is fixed, provide the steps to ensure that the error is no longer occurring.
Screenshots: Include screenshots to explain the issue better
Make at least 2 reports.
Deliverables
After completing all the exercises, you may have produced the following documents:
Bug Reports for the section A
Comments on each issue in B. The comments could be a bug report or an explanation of how each issue behaved.
An excel sheet with the Announcement functionality.
If you have done step D, include some screenshots
Comments