# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# CherryBomb -- CherryBlossom Internal Test Procedures (CDRL-14c)

21 June, 2012

- 1
- 2
…
- 63
- 64
- 65
- 66
- 67
…
- 70
- 71

UNCLASSIFIED
Cherry Bomb Program Cherry Blossom Internal Test Procedures
5.43 CW Random Link Walk Test
Description: Tests random walking of the various links of cross-referenced CW
pages.
Setup: assumes 5.1
Run: Spend 5 minutes randomly navigating CW via the many links on each page.
Note your steps in case of an exception.
Pass/Fail: passes if pages render properly, with appropriate/correct information on
each page.
5.44 CW Multiple Target Decks Exceeding 150 Targets in a Mission
Test
Description: Tests that CW does not allow Target Decks to be created/edited such
that more than 150 Targets are ever in a Mission.
Setup: Assumes 4.1
Run: Log onto CherryWeb and create a new Target Deck using the ‘default Targets’
as the starter deck. At the ‘Target Deck Upload’ screen, attempt to upload the file
<CB>/CherryTree/Test/Targs150_T.txt with Upload Action set to Append. This will
attempt to add 150 targets to the Default target deck.
Pass/Fail: An error should be displayed stating that the maximum number of targets
allowed for a target deck has been exceeded.
5.45 CW Catapult (Simulated) Test
Description: Tests CW Catapult interface (in a simulated manner). In this test
setup, Margarita will be used to simulate a Catapult server, however, any locally
running Tomcat instance can be used.
Setup: Assumes 4.1. In addition, there are two ways to simulate a catapult server
described below (Catapult Server 1/2). Only one of these approaches should be
used.
Catapult Server 1: This approach relies on using the Tomcat instance running on
zakura to validate catapult data. In this approach, the Catapult URL should be
‘https://localhost’. The data will be outputted to the log file at
/var/log/cherryweb/CherryWeb.log. If this is a routine system test, then this
approach is recommended.
Catapult Server 2: This approach allows for a second Tomcat instance to be used
and allows for testing away from the production server. However, it requires an
UNCLASSIFIED
65

- 1
- 2
…
- 63
- 64
- 65
- 66
- 67
…
- 70
- 71