<commit_before>Because of the nature of BOLD, unit tests are quite limited in their
ability to determine if the application functions as intended. In order to make
it less likely that broken code goes undetected, I have opted to create this
file that contains a "manual teste suite". The entire suite of tests need not
be run each time code is committed, although it should be conducted
when tagging snapshots as "stable".

1. Ensure the navigation of activities is congruent with the design graph.
I have drawn up a graph with nodes as activities and edges as the transition
between them. (I'll eventually scan it but that's not desperate as I'll likely
be the only one doing the testing for some time).

The application should be navigated through, checking each node and edge is in
line with what's on the handwritten graph to make sure things such as the
activity lifecycle methods function as expected. This first test should be
conducted simultaneously with the following tests and last the timespan of the
testing. This is so that the application is tested in the context of the
program state changing as it when all the application's functionality is used.
(For instance, we want to ensure that the user list is actually updated when a
new user is created and then returns to the UserSelectionActivity).

Remember that one can always hit the offscreen back button (although the app is
intended to make this unnecessary ) and the expected functionality of that
should be considered in the graph. The users can also hit the home button so we
need to deal with these cases at some point too.

2.<commit_msg>added more tests to manual test suite<commit_after>Because of the nature of BOLD, unit tests are quite limited in their
ability to determine if the application functions as intended. In order to make
it less likely that broken code goes undetected, I have opted to create this
file that contains a "manual teste suite". The entire suite of tests need not
be run each time code is committed, although it should be conducted
when tagging snapshots as "stable".

1. Ensure the navigation of activities is congruent with the design graph.
I have drawn up a graph with nodes as activities and edges as the transition
between them. (I'll eventually scan it but that's not desperate as I'll likely
be the only one doing the testing for some time).

The application should be navigated through, checking each node and edge is in
line with what's on the handwritten graph to make sure things such as the
activity lifecycle methods function as expected. This first test should be
conducted simultaneously with the following tests and last the timespan of the
testing. This is so that the application is tested in the context of the
program state changing as it when all the application's functionality is used.
(For instance, we want to ensure that the user list is actually updated when a
new user is created and then returns to the UserSelectionActivity).

Remember that one can always hit the offscreen back button (although the app is
intended to make this unnecessary ) and the expected functionality of that
should be considered in the graph. The users can also hit the home button so we
need to deal with these cases at some point too.

**TESTS**

CreateUserActivity:
1. Click "Create User" without entering a single character. Toast should
request a username.
2. Enter characters and then press "Create User". New user should be
displayed in the UserSelection activity.

MainActivity:
1. Currently selected user's name should be visible in top left.

RecordActivity:
1. Press cancel, no new files should be in recording (currently broken).
2. Press save without pressing the record button. 44 byte file should appear
in recordings with corresponding JSON file filled with the fields
"date_string", "recording_name", "creatorUUID", "uuid".
3. Record a segment and press "save" without hitting pause. The file should
play as expected.
4. Record a segment, press pause and then "save". The file should play as
expected.
5. Record a segment with intermittent pauses and then save. The file should
play as expected.
6. Record "November Rain" and examine the recording to ensure it plays as
expected.
7. Record a segment, press cancel and ensure no files exist.
8. Record a segment, press pause, then cancel and ensure no files exist.

RecordingSelectionActivity:
1.
	- Ensure that the recordings directory has three files: "A", "B", and an
	unnamed file. The unnamed file should appear as it's UUID, while the other
	two appear with their respective names. 
	- Press "alphabetical" and ensure that the list sorts as expected.
	- Press "date" and ensure that the list sorts as expected.
2. Generate 1000 files and test for lag.

RespeakActivity:
1. Press cancel, no new files should be in recording (currently broken).
2. Take a short recording (only a couple seconds), and attempt to respeak after
replay has ended.
3. Start respeaking and say something (ensuring the replaying stops); pause the
respeaking; resume; say something and ensure the replaying stops. Listen to the
respeaking to ensure it is as expected.
4. Hit the home button and make sure it pauses (currently broken)

Listen Activity:
1.
-Choose an audio file.
-Start playing
-Skip around to various parts of the file.
-Once the recording has finished playing, select a point in the recording, and
press play and ensure it behaves as expected.
-Press the home button during playing; resume the app; and ensure that it is
auto paused with the button changing appropriately so that one can resume
playing (currently broken).
{'fraction_non_alphanumeric': 0.0357653791130186, 'fraction_numerical': 0.004828326180257511, 'mean_word_length': 4.424830261881668, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '565771', 'n_tokens_mistral': 1340, 'n_tokens_neox': 1289, 'n_words': 923}