action #62171
closed
coordination #60071: [functional][y][epic] SLE 15 SP2 feature testing
action #60077: [functional][y][SLE-7216][SLE-7104] Test offline installer
[SLE][functional][y] Automate testing of full installer
Added by JRivrain over 4 years ago.
Updated over 4 years ago.
Description
Motivation¶
New full installer allows offline installations without registration. Should be tested.
Acceptance criteria¶
- Scope of the test suites to be executed for full medium is defined
- Test scenarios from step 1. are executed for full medium
Suggestions¶
- copy allmodules+allpatterns, but offline. Worked in manual tests, though some steps will have to be modified, in particular addon_products_sle, as at the end of scc_registration we would end with a list of additional addon-products. So that's either modification of a module or a new module.
And/or :
- we should have scenario where we register system after installation with full medium
- Select first SAP at product selection, then add all available extensions, then choose HA as system role. Then verify that system has SAP and HA. or, split it in two tests.
Scope¶
Sle 15 SP2
- Due date set to 2020-02-11
- Priority changed from Normal to High
- Subject changed from [SLE][functional][y] Automate testing of offline (full) installer to [SLE][functional][y] Automate testing of full installer
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 5.00 h
I managed to clone allmodules+allpatterns and run it offline : http://waaa-amazing.suse.cz/tests/11254# using the following parameters, copied from offline_install+skip_registration:
ADDONS=all-packages INSTALLONLY=1 SCC_REGISTER=' ' OFFLINE_SUT=1 ISO=SLE-15-SP2-Full-x86_64-Build134.1-Media1.iso ISO_MAXSIZE=9469952000 FLAVOR=Full
- Status changed from Workable to In Progress
I would propose to create 3 sub-tickets for this, in order to:
1- Enable offline installation/registration for all backends/architectures instead of just skip_registration
2- Register after install: Either modify scc_registration.pm to be launched from desktop/ncurses after first_boot, or create a "console" module ( using SUSEconnect ).
3- Adapt allmodules+allpatterns to work offline as in comment #5.
We could have only one test suite that runs everywhere, but we may prefer to keep at least one which does a standard online install with the full installer.
EDIT: there is a module for post-registration in functional group. and they are testing various scenarios that cover online install, skip registration... So what they do not test is full offline install with allmodules+patterns, and then post-registration. So, I'd rather do only 1 ticket to create that new test suite, then enable it everywhere.
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Closed
Not sure why I had put this back to "in progress". Maybe a miss-clic, or maybe about the point 3 "Select first SAP at product selection, then add all available extensions, then choose HA as system role. Then verify that system has SAP and HA. or, split it in two tests"
For the point 3, HA and SAP installs are covered by SAP and HA teams already.
- Status changed from Closed to Resolved
- Due date set to 2020-03-10
due to changes in a related task
- Due date changed from 2020-03-10 to 2020-03-24
due to changes in a related task
- Due date changed from 2020-03-24 to 2020-04-07
due to changes in a related task
- Copied to coordination #65307: [SLE][functional][y][epic] Extend automated testing coverage for full installer added
- Copied to coordination #65313: [SLE][functional][y][epic] Extend automated testing coverage for full installer added
- Copied to deleted (coordination #65313: [SLE][functional][y][epic] Extend automated testing coverage for full installer)
- Start date set to 5000-01-01
due to changes in a related task
Also available in: Atom
PDF