action #138095
closedcoordination #138077: [qe-core] Packages in Python Reduced Stack
[qe-core] Add a new test to verify Python-BeautifulSoup4
100%
Description
Introduce a new test to install and verify Python-BeautifulSoup4. Ensure that Python-BeautifulSoup4 is installed, and then write a sample script that imports Python-BeautifulSoup4 to scrape data from websites. Finally, verify the results of the script.
https://pythonprogramming.net/introduction-scraping-parsing-beautiful-soup-tutorial/
Updated by amanzini about 1 year ago
- Assignee set to amanzini
Some starting questions:
- on which testsuite is better to schedule this new test?
- should run on all products and version, or only on specific ?
Note:
- the library itself already contains a comprehensive test suite, and includes also fuzzing.
Updated by dvenkatachala about 1 year ago
Currently, we have python3_new_version_check and python3_setuptools tests are in the mau-extratests1 test suite - https://openqa.suse.de/tests/12566474#. We can add these tests for 15-SP4 and 15-SP5 on all architectures. Maybe later, we can move all Python-related tests as a separate test suite.
Andrea and I discussed and decided to install and verify python-beautifulSoup4 in the test environment, without focusing extensively on functionality. As bs4 already has an internal test suite and undergoes fuzz testing. Therefore, functional testing may be considered out of scope. What we can do is test it within the SUSE environment
Updated by amanzini about 1 year ago
- Status changed from Workable to In Progress
Updated by amanzini about 1 year ago
- % Done changed from 0 to 50
It might be a good idea to group all the python test in a specific testsuite.
Should we schedule also for Tumbleweed / Leap / ALP ?
Updated by amanzini about 1 year ago
- Status changed from In Progress to Feedback
Updated by dvenkatachala about 1 year ago
That's the plan. Once we move all Python-related tests to a separate test suite, we can schedule the same tests in Tumbleweed and LEAP. I am not sure about ALP. Let's check with Santi.
I will create a new ticket to move all python-related tests to separate test suite.
Updated by amanzini about 1 year ago
- Status changed from Feedback to In Progress
looking at the previous python tests, like
python3_new_version_check and python3_setuptools seems there is some duplicate code that we can use in this test as well. How about refactoring common functions like get_python3_specific_release() remove_installed_pythons() and so on in a "python_versions" lib package ?
Updated by amanzini about 1 year ago
- Status changed from In Progress to Feedback
- % Done changed from 50 to 80
updated PR, dealing with multiple python versions and refactored common code in a separate library.
Updated by amanzini about 1 year ago
- Status changed from Feedback to Resolved
- % Done changed from 80 to 100
Updated by szarate about 1 year ago
- Related to action #138401: [qe-core] Move all Python-related tests to a separate test added