IntelOwl icon indicating copy to clipboard operation
IntelOwl copied to clipboard

Speed up unit-test

Open mlodic opened this issue 4 months ago • 1 comments

After the new unit-tests for analyzers (https://github.com/intelowlproject/IntelOwl/actions/runs/16919533634/job/47941937348?pr=2886), we can see that the full pipeline is quite slow but that's not caused by the added tests. There are some tests that take a lot of seconds while they shouldn't. We should list and review them one by one to reduce the amount of time required to run the full pipeline.

Examples: test_subclasses (tests.api_app.ingestors_manager.test_classes.IngestorTestCase.test_subclasses) ... ok-dokey (18.214010s) test_pull (tests.api_app.analyzers_manager.test_views.AnalyzerConfigViewSetTestCase.test_pull) ... ok-dokey (15.476543s) test_urls (tests.api_app.analyzers_manager.file_analyzers.test_doc_info.DocInfoTestCase.test_urls) ... ok-dokey (36.010417s) test_analyze_file__pcap (tests.api_app.test_api.ApiViewTests.test_analyze_file__pcap)....ok-dokey (7.632454s) -> this one fails too test_job_rescan__observable_playbook (tests.api_app.test_api.ApiViewTests.test_job_rescan__observable_playbook) ... ok-dokey (13.045382s)

mlodic avatar Aug 13 '25 16:08 mlodic

This issue has been marked as stale because it has had no activity for 30 days. If you are still working on this, please provide some updates.

github-actions[bot] avatar Sep 14 '25 09:09 github-actions[bot]

Hi! I would like to work on this issue. Could you please assign it to me?

NobleCoder69 avatar Dec 10 '25 14:12 NobleCoder69