From e7f2a83e16e0c354bdf12ecc2974d3dc678be359 Mon Sep 17 00:00:00 2001 From: Karim shoair Date: Sat, 23 Nov 2024 16:12:00 +0200 Subject: [PATCH] Increasing the time a little bit for the performance test It's prolonged on GitHub Actions for obvious reasons --- tests/parser/test_general.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/parser/test_general.py b/tests/parser/test_general.py index 074ad40..386680a 100644 --- a/tests/parser/test_general.py +++ b/tests/parser/test_general.py @@ -278,7 +278,7 @@ class TestParser(unittest.TestCase): self.assertEqual(len(elements), 5000) # Converting 5000 elements to a class and doing operations on them will take time # Based on my tests with 100 runs, 1 loop each Scrapling (given the extra work/features) takes 10.4ms on average - self.assertLess(end_time - start_time, 0.1) + self.assertLess(end_time - start_time, 0.2) # Use `coverage run -m unittest --verbose tests/test_parser_functions.py` instead for the coverage report