From 1298dce3db9571a0907404cd3af09df948255d9e Mon Sep 17 00:00:00 2001
From: Star Rauchenberger <fefferburbia@gmail.com>
Date: Mon, 18 Dec 2023 10:46:24 -0500
Subject: Lingo: Tests no longer disable forced good item (#2602)

The static class with the "disable forced good item" field is gone. Now, certain tests that want to check for specific access progression can run a method that removes the forced good item and adds it back to the pool. Tests that don't care about this will collect the forced good item like normal. This should prevent the intermittent fill failures on complex doors unit tests, since the forced good item should provide enough locations to fill in.
---
 testing.py | 2 --
 1 file changed, 2 deletions(-)
 delete mode 100644 testing.py

(limited to 'testing.py')

diff --git a/testing.py b/testing.py
deleted file mode 100644
index 22fafea..0000000
--- a/testing.py
+++ /dev/null
@@ -1,2 +0,0 @@
-class LingoTestOptions:
-    disable_forced_good_item: bool = False
-- 
cgit 1.4.1