action #13174
closed
[functional][u] ftp integration tests
Added by scarabeus_iv over 8 years ago.
Updated over 4 years ago.
Target version:
SUSE QA - Milestone 30
Description
Test case¶
- Install vsftpd and some ftp client
- Configure various ftp scenarios as described in QAM test reports (ssl, non-ssl, with users, anonymous)
- For each scenario verify uploading and downloading of files works
- Try some unprivileged access over ftp to verify there is no bug in regexp matching filters in vsftpd (as per last vsftpd update testreport)
Existing test module¶
elsif (get_var('QAM_VSFTPD')) {
set_var('INSTALLONLY', 1);
if (check_var('HOSTNAME', 'server')) {
barrier_create('VSFTPD_SUITE_READY', 2);
barrier_create('VSFTPD_FINISHED', 2);
}
boot_hdd_image;
loadtest 'network/setup_multimachine';
loadtest 'network/vsftpd';
}
Task¶
Add existing test module network/vsftpd in a test suite in functional job group. (extra_tests_textmode)
- Status changed from New to In Progress
- Assignee deleted (
scarabeus_iv)
- % Done changed from 0 to 100
djz88 if all the steps defined by scarabeus_iv in the description are satisfied, you can mark this ticket as resolved.
- Subject changed from ftp integration tests to [functional]ftp integration tests
- Target version set to Milestone 18
- Subject changed from [functional]ftp integration tests to [functional][u] ftp integration tests
- Status changed from In Progress to Workable
- Target version changed from Milestone 18 to Milestone 18
- Target version changed from Milestone 18 to future
- Status changed from Workable to New
Bulk action to set status back to "New" for older tickets which are in "future". They would need to be revisited in time when we come up with a defined plan and assign to a milestone.
- Priority changed from Normal to Low
let's focus more on improving our current tests and workflows first. Putting to "holding tank" :)
This was already implemented, however we need to enable them for new products and check if they're running on any scenario from the U team.
- Priority changed from Low to High
This is low hanging fruit. this can be added in extra_tests_textmode, or a better place. @Sergio What do you think?
- Description updated (diff)
- Status changed from New to Workable
- Target version changed from future to Milestone 30
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to dheidler
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF