Locust issues

Daniel Múčka found:

AUTHTOKEN could have been inserted using .env file. — Locust works. No failures detected in the scenario. — For the sequential scenario, for 10 users I was getting 10-14% failure rate. — The scenarios make sense. However, I really think a scenario where an external, nonauthenticated user is trying to look up flights is missing

Michal found:

Locust:

OK

Why is:

# @task()
def get_unused_planes(self):

Commented out? That is the most interesting task.

/ERROR/locust.user.task: list.remove(x): x not in list
Traceback (most recent call last):
  File "C:\Editors\Python3.10\lib\site-packages\locust\user\task.py", line 347, in run
    self.execute_next_task()
  File "C:\Editors\Python3.10\lib\site-packages\locust\user\task.py", line 372, in execute_next_task
    self.execute_task(self._task_queue.pop(0))
  File "C:\Editors\Python3.10\lib\site-packages\locust\user\task.py", line 384, in execute_task
    task(self)
  File "C:\MUNI\last\Java\M3\airport-manager\runnable-scenario\runnableScenario.py", line 462, in deleteFlight
    flights.remove(flightToDelete)
ValueError: list.remove(x): x not in list

I encountered this error, but it did not halt the test, and since it was a removal it likely had no effect on the results either, so I am just throwing it out here.