File List Progress

FILE_LIST_PROGRESS_COMPLETE

See the source code.

This test verifies that requesting a file list for a folder containing many files sends a series of ListProgress messages until the full FileListResponse arrives, and that the backend remains responsive afterward.

1. Frontend sends: FILE_LIST_REQUEST (FileListRequest) for a large folder

   directory = "set_QA/set_lotsFiles2"
   

2. Backend returns: a series of LIST_PROGRESS (ListProgress) messages followed by FILE_LIST_RESPONSE (FileListResponse)

Check 1: the FILE_LIST_RESPONSE should satisfy:

• Should arrive within 60000 ms

• FILE_LIST_RESPONSE.success = True

3. Frontend sends: FILE_LIST_REQUEST (FileListRequest) for a different folder to verify backend health

   directory = "set_QA"
   

Check 2: the backend health check should satisfy:

• FILE_LIST_RESPONSE is defined

• FILE_LIST_RESPONSE.success = True

• FILE_LIST_RESPONSE.directory contains “set_QA”

FILE_LIST_PROGRESS_CANCELLATION

See the source code.

This test verifies that a file list request for a large folder can be cancelled mid-progress using StopFileList, and that the backend remains responsive after cancellation.

1. Frontend sends: FILE_LIST_REQUEST (FileListRequest) for a large folder

   directory = "set_QA/set_lotsFiles2"
   filter_mode = 0
   

2. Backend begins returning: LIST_PROGRESS (ListProgress) messages

3. After receiving the first ListProgress message, Frontend sends: STOP_FILE_LIST (StopFileList)

   file_list_filter_mode = 0
   

Check 1: the cancellation should succeed:

• At least one LIST_PROGRESS message should have been received before cancellation

• The LIST_PROGRESS.percentage field should be defined

4. Frontend sends: FILE_LIST_REQUEST (FileListRequest) for a different folder to verify backend health

   directory = "set_QA"
   

Check 2: the backend health check should satisfy:

• FILE_LIST_RESPONSE is defined

• FILE_LIST_RESPONSE.success = True

• FILE_LIST_RESPONSE.directory contains “set_QA”