Ref. Ares(2013)215967 - 19/02/2013
EUROPEAN COMMISSION
Legal service
IT Group
European Commission
PDFMerge - general test case
Date: 13/02/2013
Version: 1.0
Authors:
Revised by:
Approved by:
Public:
Reference Number:
Commission européenne, B-1049 Bruxelles / Europese Commissie, B-1049 Brussel - Belgium. Telephone: (32-2) 299 11 11.
Commission européenne, L-2920 Luxembourg. Telephone: (352) 43 01-1.
link to page 4 link to page 4 link to page 4 link to page 4 link to page 5 link to page 6 link to page 6 link to page 6 link to page 6 link to page 6 link to page 7 link to page 7 link to page 7 link to page 8 link to page 8
TABLE OF CONTENT
•
1. INTRODUCTION ............................................................................................................................... 4
1.1. Purpose of this document ..................................................................................................
...................... 4
1.2. Objectives ................................................................................................................
................................ 4
1.3. Dependencies..............................................................................................................
............................. 4
•
2. OUTLINE OF THE TEST PATTERNS........................................................................................... 5
•
3. TESTS.................................................................................................................................................. 6
3.1. STEP 1 – MERGING DOCUMENTS ................................................................................................
.... 6
3.1.1. Merging documents .......................................................................................................
....................... 6
3.2. STEP2 – FILE CLEANUP
....................................................................................................................... 6
3.2.1. Check that no obsolete file is left in the merge folder .................................................................
......... 6
3.2.2. Check that no obsolete file is left in the download folder ..............................................................
...... 7
3.3. STEP3 – EXCEPTION HANDLING
...................................................................................................... 7
3.3.1. Check that insufficient remaining disk space is properly handled by PDFMerge downloader
............ 7
3.3.2. Check that insufficient remaining disk space is properly handled by PDFMerge
................................ 8
3.4. STEP4 – LOAD TESTING
...................................................................................................................... 8
Solon - General Test Case -
Page 2/8
Document Version 1.0 dated 13/02/2013
History of document
Version Date
Comment
Modified
Pages
1.0
07/02/2013 Creation of General Test Case Document for first
All
production roll-out
Solon - General Test Case -
Page 3/8
Document Version 1.0 dated 13/02/2013
1. INTRODUCTION
1.1. Purpose of this document
This is a generic test case to be executed before any production roll-out of the software.
1.2. Objectives
The rationale beyond this document is to provide a set of minimal testing patterns whose
completion provides a reasonable insurance about reliability of main software functions.
Those patterns are extensive, meaning that their path covers the main functions of the application.
Nevertheless, due to the infinite possibility of data and action sequence combinations within the
scope of the application, it cannot be qualified as an exhaustive test.
It is the basic testing procedure to be associated to more specific ones when specific modules are
undergoing evolutions.
Unless specified, it can be executed by people having reasonable computer-literacy without any
prior knowledge of the software application or its business domain.
1.3. Dependencies
This has been done for a user having at least the following profile:
• Be a Tester
•
PDFMerge test case: http://sjdapps/apps/sj-solon/?fa=documentservice.pdfmergetest
• Have access to the first test document:
http://sjdapps/apps/solon/index.cfm?fuseaction=documentpropertysheet.view&docid=
Ares(2012)36737&showdetailattr=true&repository=ares
• Have access to the second test document:
http://sjdapps/apps/solon/index.cfm?fuseaction=documentpropertysheet.view&docid=080166
e480abdd79&showdetailattr=true&repository=ares
Solon - General Test Case -
Page 4 / 8
Document Version 1.0 dated 13/02/2013
2. OUTLINE OF THE TEST PATTERNS
The test case pattern breakdown is presented in the table hereafter. The different steps are to be
executed in sequence.
Each step is itself made of unitary steps. Further to test execution, each unitary step can receive a
OK (compliant result) or NOK (non-compliant result) status.
If one of the unitary steps gets a NOK status, it is required as far as possible to resume testing
procedure. In case it becomes obviously impossible, the test is stopped and the project leader is to
be informed without delay.
As far as possible, the test steps are to be executed with data given as example. In some
situations, it will not be possible due to differences between the Test and Production
environments. In this case, the step result still can be positive but it is required to keep track of
this as a remark in the Result column.
ID
Libelle
Condition 1
Condition 2
Result
Merging
documents
File cleanup of merged
documents
File cleanup of downloaded
documents
Exception handling for document
downloading
Exception handling for document
merging
Load
testing
Unmodified
first
Make sure you 5 merged PDF
test document & have an active documents
attachments
ECAS session
before running the
load test
Solon - General Test Case -
Page 5 / 8
Document Version 1.0 dated 13/02/2013
link to page 6
3. TESTS
3.1. STEP 1 – MERGING DOCUMENTS
3.1.1. Merging documents
Description Expected
Result
OK/NOK
Use the URL provided by the project leader to access
the first test document The document property sheet appears
OK
propertysheet.
Tick on all checkboxes marking the files to be merged
Boxes are ticked
OK
Press the PDFMerge button
The merge button is disabled for a few
OK
seconds
An animation shows that an operation is on-
going
Eventually, the merged PDF file appears in a
new window
Look at the resulting PDF file
The file is made of the PDF documents
OK
ticked on the property sheet.
3.2. STEP2 – FILE CLEANUP
3.2.1. Check that no obsolete file is left in the merge folder
Description Expected
Result
OK/NOK
Run a PDF Merge operation as in 3.1.1
The PDF files are merged.
OK
Solon - General Test Case -
Page 6 / 8
Document Version 1.0 dated 13/02/2013
link to page 6 link to page 6 link to page 6 link to page 6
Wait for 6 minutes
Run a PDF Merge operation as in 3.1.1
The PDF files are merged.
OK
Open the Test case page: http://sjdapps/apps/sj-
In the merge folder, no file is more than 5
OK
solon/?fa=documentservice.pdfmergetest
minutes old (no value above 5 should appear
in the Minutes column for this folder)
3.2.2. Check that no obsolete file is left in the download folder
Description Expected
Result
OK/NOK
Run a PDF Merge operation as in 3.1.1
The PDF files are merged.
OK
Wait for 6 minutes
OK
Run a PDF Merge operation as in 3.1.1
The PDF files are merged.
OK
Open the Test case page: http://sjdapps/apps/sj-
In the CF download folder, no file is more
OK
solon/?fa=documentservice.pdfmergetest
than 5 minutes old (no value above 5 should
appear in the Minutes column for this folder)
3.3. STEP3 – EXCEPTION HANDLING
3.3.1. Check that insufficient remaining disk space is properly handled by PDFMerge downloader
Description Expected
Result
OK/NOK
On the test case PDFMerge downloader test case setup, set the PDFMerge test The Minimum free disk space threshold is
OK
settings to "download"
increased
Run a PDF Merge operation as in 3.1.1 using this document. instead
PDF Downloader stops, Solon displays an
OK
error message to the user and sends a mail to
the si support mailbox stating that the
PDFMerge downloader encountered a low
Solon - General Test Case -
Page 7 / 8
Document Version 1.0 dated 13/02/2013
link to page 6
disk space condition.
3.3.2. Check that insufficient remaining disk space is properly handled by PDFMerge
Description Expected
Result
OK/NOK
On the test case PDFMerge downloader test case setup, set the PDFMerge test The Minimum free disk space threshold is
OK
settings to "merge"
increased.
Run a PDF Merge operation as in 3.1.1 using this document. instead
PDFMerge displays a message to the user
OK
and sends a mail to the si support mailbox
stating that it encountered a low disk space
condition.
3.4. STEP4 – LOAD TESTING
Description Expected
Result
OK/NOK
On the test case PDFMerge downloader test case setup, click on the link to the The sample document property sheet is
OK
sample document
displayed in a new tab or new window
Click on the Run Load Test button
5 new tabs (or windows) appear, each one
OK
contains a merged PDF file.
4. TEST PLAN OUTCOME
The test plan ran successfully
Solon - General Test Case -
Page 8 / 8
Document Version 1.0 dated 13/02/2013
Document Outline