Project

General

Profile

Actions
Copy link

action #138095

closed

coordination #138077: [qe-core] Packages in Python Reduced Stack

[qe-core] Add a new test to verify Python-BeautifulSoup4

Added by dvenkatachala 6 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
amanzini
Category:
New test
Target version:
QA - QE-Core: Ready
Start date:
2023-10-17
Due date:
% Done:

100%

Estimated time:
Difficulty:

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/

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #138401: [qe-core] Move all Python-related tests to a separate testResolveddvenkatachala2023-10-24

Actions
Actions
Copy link
 #1

Updated by amanzini 6 months 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:

Actions
Copy link
 #2

Updated by dvenkatachala 6 months 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

Actions
Copy link
 #3

Updated by amanzini 6 months ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #4

Updated by amanzini 6 months 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 ?

Actions
Copy link
 #5

Updated by amanzini 6 months ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #6

Updated by dvenkatachala 6 months 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.

Actions
Copy link
 #7

Updated by amanzini 6 months 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 ?

Actions
Copy link
 #8

Updated by amanzini 6 months 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.

Actions
Copy link
 #9

Updated by amanzini 6 months ago

  • Status changed from Feedback to Resolved
  • % Done changed from 80 to 100
Actions
Copy link
 #10

Updated by szarate 6 months ago

  • Related to action #138401: [qe-core] Move all Python-related tests to a separate test added
Actions
Copy link

Also available in: Atom PDF