ODK Briefcase testing plan

	A	B	C
1	Test Summary	Step	Expected Result
2	Pull and export of 100 submissions with repeated groups.	User pulls and exports more than 100 submissions with repeated groups.	All submissions are visible in storage directory and .csv file.
3	Cmd - Export	User uses command line to export form data into CSV file, without -e prefix.	Export should be successful. CSV file should be created.
4	Cmd - Export	User uses command line to export form data into CSV file, with -e prefix.	Export should be successful. CSV file should be created.
5	Cmd - Export	User exports a form but he does not add ".csv" in filename.	Export should be successful. CSV file should be created There should not be any other text file with used filename.
6	Settings - storage location.	User clicks on Clear button next to storage directory.	Path to storage location should be removed.
7	Settings - storage location.	User clicks on Choose button. User selects another storage location.	Path to new storage location should be visible. Storage location should be changeable.
8	Settings - storage location.	User deletes storage directory manually. User relaunches briefcase.	No error message should display in cmd. Briefcase should run Welcome window should display. User should be able to set storage directory.
9	Settings - storage location.	User moves storage directory to another folder User relaunches briefcase.	No error message should display in cmd. Briefcase should run. Welcome window should display. User should be able to set storage directory.
10	Settings - HTTP Proxy	User has Settings tab opened.	There should be default host number 127.0.0.1 visible. 8080 should be default Port value
11	Settings - HTTP Proxy	User clicks on Use HTTP Proxy checkbox.	Host and Post fields should be enabled.
12	Settings - HTTP Proxy	User manipulates port value by using arrows.	Port value should be changeable.
13	Settings - HTTP Proxy	User sets 999 as port value.	User is able to use both up and down arrows.
14	Settings - HTTP Proxy	User unchecks Use HTTP Proxy checkbox.	Host and Port fields should be grayed out. Both should be returned into default value.
15	Settings - HTTP Proxy	User set "Use HTTP Proxy" checkbox. User removes content of Host field. User goes to pull/push tab. User logs in to aggregate User uses Briefcase.	User should be able to log in to aggregate. User should be able to use briefcase. No error messages should be displayed.
16	Settings - HTTP Proxy	User closes Briefcase. User relaunches Briefcase.	The default content of Host field should be restored.
17	Export - invalid submission	User breaks manually a submission. User tries to export broken submission.	Broken submission should not be exported. Export status should be message about x exported submission from y submissions in general. No error messages should be visible.
18	Export - form with audit file	User sends some submissions of form with audit from Collect to Aggregate. User pulls from aggregate forms with audits. User exports forms with audit.	Forms should be exported successfully. Media folder should be created in export directory, csv name should be form-instanceid.csv To each form with audit there should be created separate csv file formName - audit.csv. User should be able to open both files. Audit file should have columns: event, node, start and end
19	Export - form with audit file	User exports the same form twice.	Individual audit files in media folder should not be doubled. Individual audit files should not be numerated. Content of individual audit should not be doubled. Content of form.csv and form - audit.csv should be doubled.
20	Export - form with audit file	Export a different form with audit files.	New individual audit files should be created in media folder. Individual audit files should not be numerated.
21	Export - form with audit file	Choose to overwrite existing files checkbox and export again form with audit.	Content of Form.csv and Form - audit.csv should not be doubled.
22	Export - form with audit file		There should not be any errors in log file.
23	First run - java 9	User runs briefcase built on java 8 on machine with java 9.	Briefcase should run successfully. No errors is console should appear. User is able to use briefcase.
24	Export - Export button behavior	Open Export tab.	Export button should be enabled by default
25	Export - Export button behavior	Click on Export button	Dialog message should appear "No forms have been selected"
26	Export - Export button behavior	Choose some forms form the list Click on Export button	Dialog message "Some forms are missing their export directory. Please, ensure that there's default export directory or that you have set one in all custom configuration"
27	Export - Export button behavior	Choose encrypted form from export list. Click on Export button	Dialog message with information that there is no export dir and pem key file location should appear.
28	Export - Export button behavior	Set export directory. Try to export encrypted form again	Dialog message " The form is encrypted. Please, configure a PEM file" should appear.
29	Pull - log in to aggregate's server - negative cases	User chooses Pull from: Aggregate server. User clicks on Configure button.	Aggregate Server Configuration window should appear.
30	Pull - log in to aggregate's server - negative cases	User sets aggregate credentials without specifying http protocol User clicks on connect button.	Error "no protocol" should appear.
31	Pull - log in to aggregate's server - negative cases	User accepts error message.	Log in widow should be visible and cursor should not remain busy.
32	Pull - log in to aggregate's server - negative cases	User enters URL address with trailing spaces. (before or after url address)	Enter URL with trailing spaces shouldn't cause any errors. Spaces should be trimmed.
33	Pull - log in to aggregate's server - negative cases	User tries Google account credentials to log in to aggregate server.	Warning "Wrong Credentials" should be displayed.
34	Pull - log in to aggregate's server - negative cases	User accepts error message.	Log in widow should be visible and cursor should not remain busy.
35	Pull - log in to aggregate's server - negative cases	User tried to connect to server with invalid credentials. User accepts error message. User corrects the password.	Connection fails, user see "Wrong credentials" error dialog. Log in widow should be visible and cursor should not remain busy. After password correction, connection succeed.
36	Push - log in to aggregate's server - Remember passwords	Remember passwords unchecked. User logs to aggregate which requires credentials. User closes briefcase. User relaunch briefcase.	After relaunching briefcase connection should be reset.
37	Push - log in to aggregate's server - Remember passwords	User chooses Remember Passwords. User logs to aggregate which requires credentials. User closes briefcase.	After relaunching briefcase connection should be restored. Push list should be filled.
38	Push - log in to aggregate's server - Remember passwords	Remember passwords unchecked. User logs to aggregate which do not requires credentials without input credentials. User closes briefcase. User relaunches briefcase.	After relaunching briefcase connection should be restored.
39	Push - log in to aggregate's server - Remember passwords	User chooses Remember Passwords. User logs to aggregate which do not requires credentials with credentials. User closes briefcase. User relaunches briefcase.	After relaunching briefcase connection should be restored.
40	Export - GeoJson file	Choose "Include GeoJson export" checkbox on Default Export Configuration. Export form with some geo locations. Open http://geojson.io and load there .geojson file.	Checkbox should be selected In export directory .csv file and .geojson file should be created. geojson file should be loaded successfully no error messages should be displayed Map view should be visible.
41	Export - GeoJson file	Export forms which does not include geo locations data.	Empty .geojson file should be created.
42	Export - GeoJson file	Deactivate "Include GeoJson export" on Default Export Configuration. Choose "Yes" for Include GeoJson export on Individual Export Configuration window. Export form with geoshapes, geotrace Open http://geojson.io and load there .geojson file.	GeoJson file should be created in export directory. Geoshapes and geotraces should be visible on the map view
43	Export - GeoJson file	Deactivate checkboxes on Default and Individual export configuration windows Export form with geo locations.	GeoJson file should not be created.
44	Export - Export tab' UI	User opens Export tab.	There is "Set Default Configuration" button. Below the button there should be information "To override the default configuration for each form, press the gear icon". List of the forms shouldn't be overlaped by scroll in the right. There should be "Select All" button enabled. Export button should not be disabled. There shouldn't be "Cancel" button.
45	Export - Export tab' UI	User clicks on "Set Defaulf Configuration" button.	"Default export configuration" window should appear. There should be fields: Export directory, PEM file location, Start date (inclusive) and End date (inclusive), next to them there should be Choose buttons. Export media files should be checked by default. Only Cancel button should be enabled. All text boxes should be unified.
46	Export - Export tab' UI	User clicks on Choose button next to Export Directory field.	File manager should appear.
47	Export - Export tab' UI	User chooses export directory. User chooses OK button.	OK and Clear All buttons should be enabled.
48	Export - Export tab' UI	User clicks on OK button.	"Default export configuration" window should disappear. "Set Default Configuration" button should not be visible. "Edit Default Configuration" button should be visible and active.
49	Export - encrypted form - java 10	User exports encrypted forms on briefcase run on java 10.	Forms should be exported successfully.
50	Cmd - Export - Exclude media files	User uses command line to export instances but exclude media export. User uses -em prefix	Instances without media should be exported successfully.
51	Google analytics tracking	User opens Settings tab	Checkbox "Send usage data and crash logs to core developers" should be selected by default.
52	Google analytics tracking	User pull/push/export forms.	All user's actions should be tracked on Google Analytics. (Real-time events)
53	Google analytics tracking	User does some cmd actions.	Cmd actions should not be tracked on Google analytics.
54	Google analytics tracking	User deselects "Send usage data and crash logs to core developers" checkbox.	All actions should not be tracked on Google analytics.
55	Export - bulk export of encrypted forms	User exports bulk encrypted forms.	Forms are exported successfully.
56	Cmd - Export with GeoJson file	Use cmd to export form with geo locations without using -ig param Use cmd to export form with geo locations with using -ig param Open .geojson file on http://geojson.io	.csv file should be created and .geojson file should not be created. .csv and .geojson files should be created File should be opened Map should be visible No errors should be visible.
57	Cmd - Export with GeoJson file	Repeat all steps for form with geotrace and geoshape widgets.	Results should be the same.
58	Export - Pull before export	User chooses "Remember password" options in Settings.	Pull before export option should be enabled now on Export tab - Default Configuration Window.
59	Export - Pull before export	User selects Pull before export checkbox on Default Export Configuration.	Pull before export option should be active now.
60	Export - Pull before export	User has to pull form for the first time manually on pull tab. User pulls two forms.	Both forms should be displayed on export list.
61	Export - Pull before export	User fill submission of both forms using ODK Collect. User sends filled submissions to ODK Aggregate.	Both submission should be visible on ODK Aggregate.
62	Export - Pull before export	For one form user chooses Inherit option in Individual configuration window for Pull before export. For the second form user chooses "No" for Pull before export checkbox. User choose to export both forms.	Exported .csv file of the first form should contain submission just sent to ODK Aggregate. Exported .csv file of the second form should not contain just sent submission to aggregate.
63	Export - Pull before export	User fills another submission of the first form and sends it to aggregate. User deactivate Pull before export checkbox on Default Export Configuration window. User chooses on Individual Export Configuration for the first form "No" in Pull before export. User chooses on Individual Export Configuration for the second form "Yes" for Pull before export. User exports both forms.	New submission of the first form should not be included in exported csv. Submission of the second form should be visible in exported csv.
64	Export - Pull before export	User clears Individual Export Configuration of both forms. User selects Pull before export checkbox on Default Export Configuration window. User exports the first form.	New submission of the form should be pulled and exported.
65	First run - java 10	User runs briefcase built on java 8 on machine with java 10.	Briefcase should run successfully. No errors is console should appear. User is able to use briefcase.
66	Pull before export source - anonymous access	Remember password checkbox must be selected. On pull tab input aggregate's url with anonymous access allowed, do not input log in credentials. Pull the form Close Briefcase	Form should be pulled successfully and present in storage directory.
67	Pull before export source - anonymous access	Run Briefcase again Open Export tab Open forms's individual Export Configuration.	Pull before export option should be enabled.
68	Pull before export source - anonymous access	Choose Yes for Pull before export option Set Export Directory Click on OK button. Send new submission of the form from Collect to Aggregate	Submission should be visible on Aggregate.
69	Pull before export source - anonymous access	Export the form.	Just sent submission should be present in CSV file.
70	Pull before export source - anonymous access	Choose No to Pull Before Export on form's individual Export Configuration. Repeat all steps.	Just sent submission should not be present in CSV file.
71	Pull - Collect directory.	User selects "Collect Directory" in Pull data from. Reset previous connection if needed.	File manager should be displayed. User should be able to go through directories and look for odk folder. The only present filter is All files.
72	Pull - Collect directory.	User chooses odk directory.	List of form should appear.
73	Pull - Collect directory.	User pulls form from odk directory.	The form should be pulled successfully. There are no errors in cli output.
74	Push - bulk push - interruption.	User inputs correct credentials on Aggregate Server Connection window. User clicks on Connect button.	User should be successfully connected to server.
75	Push - bulk push - interruption.	User selects some forms from the push list. User clicks on Push button. User clicks on Cancel button.	Cancel button should be active. Button is not one-time usable - it can be used when it is needed. Push process should be interrupted. All push messages should be capitalized.
76	Export - 50k submissions	User exports 50k submissions.	Submissions should be exported successfully. Export shouldn't be interrupted. There should be no error messages.
77	Cmd - Export - Date range export	User uses command line to export instances from specific start date until today. Date form is yyyy/mm/dd -start yyyy/mm/dd	Instances should be exported successfully.
78	Cmd - Export - Date range export	User uses command line to export instances from specific date period. Date form is yyyy/mm/dd -start yyyy/mm/dd -end yyyy/mm/dd	Instances should be exported successfully.
79	Cmd - Export - Date range export	User uses command line to export instances from specific start date until today. Date form is yyyy-mm-dd -start yyyy-mm-dd	Instances should be exported successfully.
80	Cmd - Export - Date range export	User uses command line to export instances from specific date period. Date form is yyyy-mm-dd -start yyyy-mm-dd -end yyyy-mm-dd	Instances should be exported successfully.
81	Export - submissions with no instanceID	User pulls forms with repeated groups from odk directory (Birds, Forest Plot). User exports those forms do csv.	In csv file instances with no instanceID should be ignored. no errors should be visible, no errors in ouput
82	Export - submissions with no instanceID	User removes manually instanceId of submission of the form without repeated groups.	All submissions should be exported, submission with deleted instaceID should have blank value of that. no errors should be visible, no errors in ouput
83	Export - media files	Export media files checkbox is selected. User exports form with uploaded images and other media files like: jpg -> image/jpg 3gp -> video/3gp mp4 -> video/mp4 amr -> audio/amr	Forms should be exported. All types of media files should be uploaded. Media folder should be created in export directory.
84	Export - media files	There are two images with the same timestamp in two difference instance folders. User exports form.	One image should be renamed with the suffix '-2' in media folder.
85	Export - media files	User unchecks Export media files checkbox. User changes export directory or remove media folder. User exports form with media files.	Media folder shouldn't be created when there is no media associated with the file, while exporting to CSV.
86	Export - media files	User has export media files option set by default User chooses on individual configuration to do not export media. User exports two forms one with default and one with individual configuration.	Media files should be exported for form with default configuration Media files shouldn't be exported for form with individual configuration.
87	Cmd - Export - Multi select question	User uses command line to export form with multi select questions.	Form and instances should be exported successfully.
88	Cmd - Export - Multi select question	User uses command line to export form with multi select questions. User uses -ssm prefix.	Form and instances should be exported successfully. Answers are in Boolean form 0,1. User compares form of csv file from that case and case above.
89	Export - export with failed submission saved.	User breaks manually a submission in sd but first and last lines should remain intact. User runs briefcase/ reloads forms in sd. User exports that form with submissions.	Export should be successful No unexpected error should not be visible. Export status should be "Exported X forms from X+1 forms" In the export directory there should be created folder "Form name - errors" In this folder there should be failed submission xlm file with number 1 index.
90	Export - export with failed submission saved.	User exports that form once again.	Error folder should be refreshed. Submission in folder shouldn't be duplicated. There should be the same amount on failed submission as in the first try with the same numeric indexes.
91	Export - export with failed submission saved.	User repeats steps 1-2 for the same form.	Results should be exactly the same but for 2 failed submissions.
92	Export - export with failed submission saved.	User repeats the first step for another form.	Numeration of failed submissions for the new form should start from 1. Other results should be compliant with described above.
93	Export - Export forms to .csv file	User has chosen export directory before. User chooses forms to export from the list.	Selection highlight is extended behind Detail button. Export button should be enabled.
94	Export - Export forms to .csv file	User set default configuration. User Clicks on export button.	Export options are grayed out in the middle of export process. In the middle of export process percentage progress is visible in Export Status tab Progress bar in the left side on Export button should be visible too. Status message shouldn't show up when none of export activity has been done. After finishing export process User should see status "Exported <number of submission>" Details button should be enabled. Forms are exported in compliance with default configuration.
95	Export - Export forms to .csv file	User clicks on Details button.	Detailed Status window should appear. Status of export is visible there. Detailed Status window is not editable.
96	Export - Export forms to .csv file	User opens export directory.	There should be exported .csv files.
97	Export - Export forms to .csv file	User opens one of exported .csv files.	Submissions should be sorted chronologically by Submission Date.
98	Cmd - Pull incomplete submissions	Pull from aggregate form to one storage directory. Pull form with -ii prefix to another storage directory.	Amount of the forms should differ in storage directories. In the second try there should be more submissions then in the first one.
99	Push - aggregate's server	User opens push tab.	There should be push to Aggregate server chosen by default. Configure button should be enabled. Push button should be disabled. If there are some forms in storage directory they should be present on the push list, if not push list should remain empty.
100	Push - aggregate's server	User clicks on Configure button.	Aggregate Server Configuration window should appear. * There should be a URL, Username and Password fields, "Username cannot be a Google login; it must be an ODK Aggregate username with "Data Viewer" permissions information and Cancel and Connect button.