Update Center Wiki: UC23TD.SecurityUpdatesTests

Home Index Changes Prefs Log in »

History

Document Name	Author	Date	Modifications
UC21TD.SecurityUpdatesTests	Faouzia EL IDRISSI	20081218	First Draft
UC22TD.SecurityUpdatesTests	Faouzia EL IDRISSI	20081218	New version for UC2.2 release
UC23TD.SecurityUpdatesTests	Faouzia EL IDRISSI	20090715	New version for UC2.3 release

Purpose

The purpose of this document is to specify tests for the Security Updates feature of the Update Center2 project.

Feature description

This section summarizes what will be implemented in the Update Center 2.x project as part of the Security Updates feature. This feature description is extracted from the following issues in IssueTracker as well as from a mail send by Chris Kasso regarding the implementation :
324

: highlight security-related updates in the notifier
322

: identify security-related updates in ips
323

: highlight security-related updates in the updatetool

The following mail from Chris Kasso provides more details about the feature : QA folks,

This week I checked in the changes for issue 324:

https://updatecenter2.dev.java.net/issues/show_bug.cgi?id=324

The notifier will now highlight security updates independent of regular updates. It looks something like this:

GFV2 1 security update available

Nightly image 2 security updates available 1 other update available

I'm going to blog about this next week but I wanted to give you some input on how it works so that you can test it.

When the notifier checks for updates it will now inspect the info.keywords pkg attribute. If any of the keywords is "security" this indicates that this version of the pkg has security related changes.

For example if the notifier found that three pkgs had updates and one of those pkgs had info.keywords=security the notifier balloon would look something like this:

1 security update available 2 other updates available

To test this you will need to generate some packages that have security as a keyword in info.keywords.

For testing purposes I also added two defaults.cfg properties:

main _security_update_attr _security_update_keywords

This allows you to control which pkg attribute the notifier uses to look for the "security" keyword. The _security_update_keywords property allows you to tell the notifier what the security keywords are. There can be more than one (comma separated). These properties are only for testing purposes. We are not going to document them. But you can set them to:

_security_update_attr = info.classification _security_update_keywords = System

and the notifier will look for the keyword "System" in the info.classification pkg attribute. This makes the UC toolkit pkgs look like security updates.

I see that Manpreet just checked in the GUI side changes. These same properties should work on the GUI side as well.

Happy testing.

Chris

References

324

: highlight security-related updates in the notifier
322

: identify security-related updates in ips
323

: highlight security-related updates in the updatetool

Test Approach

The following should be considered while testing the Security Updates support :

Test Cases description

Test_ID	Test Purpose	Test Description	Expected Behavior
UC21.SecurityUpdate.F001	Check that the notifier highlights a security update for a package	Install updatetool from an architecture specific image modify defaults.cfg by setting the following attributes : _security_update_attr = info.keywords and _security_update_keywords = Security Update in the main part of defaults.cfg file Start updatetool Check that the notifier is running Start a testing repo and publish a test package Using updatetool, create a user image for the testing repository and install the available package publish an update for that package and set the attribute info.keywords to "Security Update", this is achieved by the command : pkgsend -s http://repo_host:repo_port add set name="info.keywords" value="Security Update"	When appropriate, the notifier will highlight that a security update is available for this package.
UC21.SecurityUpdate.F002	Check that the notifier manages properly a mix of security updates and non security updates for the same user image	Install updatetool from an architecture specific image modify defaults.cfg by setting the following attributes : _security_update_attr = info.keywords and _security_update_keywords = Security Update in the main part of defaults.cfg file Start updatetool Check that the notifier is running Start a testing repo and publish 2 test packages Using updatetool, create a user image for the testing repository and install the available packages publish an update for the 1st package and set the attribute info.keywords to "Security Update", this is achieved by the command : pkgsend -s http://repo_host:repo_port add set name="info.keywords" value="Security Update" publish an update for the second package without setting the info.keywords attribute	The notifier balloon shows that there is 1 security update and an other update for this image
UC21.SecurityUpdate.F003	Check that the notifier manages properly when multiple user images have security updates	Start a test repository publish 4 packages foo1@1.0-1.0, foo2@1.0-1.0, foo3@1.0-1.0, foo4@1.0-1.0 create 2 user images image1 and image2 install foo1 and foo2 in image1 install foo3 and foo4 in image 2 publish a security update for package foo1 and for package foo3	The notifier should highlight properly the security updates as well as non security updates
UC21.SecurityUpdate.F004	Check the notifier and updatetool behavior when multiple keywords are supported for security updates	Install updatetool from an architecture specific image modify defaults.cfg by setting the following attributes : _security_update_attr = info.keywords and _security_update_keywords = sec1,sec2,sec3,sec4 in the main part of defaults.cfg file Start updatetool Check that the notifier is running Start a testing repo and publish 4 packages : foo1, foo2, foo3 and foo4 Create a user image and install the 4 packages PUblish updates for the 4 packages and for foo1 update, set the info.keywords attribute to sec1, for foo2 set info.keywords attribute to sec2, for foo3 set info.keywords attribute to sec3,for foo4 set info.keywords attribute to sec4	The notifier should highlight that there are 4 security updates
UC21.SecurityUpdate.F005	Check that the notifier does not highlight as security update an update for a package where the info.keywords attribute value does not match what is in defaults.cfg	Start a test repo Publish a package to tis repo Create a user image and install this package publish an update for this package and set the info.keywords attribute to "Security"	Check that the notifier does not highlight this update as a Security Update
UC21.SecurityUpdate.F006	Check that the notifier highlight the presence of security updates if at least one update level is considered as seurity update	on a testing repo, publish a test package Create a user image and install this package Publish a first update without setting the info.keywords attribute publish a second update by setting the info.keywords to a value matching the configuration in defaults.cfg Publish a third update without setting the info.keywords attribute	Check that the notifier highlights the presence of a security update
UC21.SecurityUpdate.F007	Check that the updatetool highlights Security Updates in the Available Updates View	install updatetool from an architecture specific image modify defaults.cfg by setting the following attributes : _security_update_attr = info.keywords and _security_update_keywords = Security Update in the main part of defaults.cfg file Start updatetool Start a testing repo and publish a test package Using updatetool, create a user image for the testing repository and install the available package publish an update for that package and set the attribute info.keywords to "Security Update", this is achieved by the command : pkgsend -s http://repo_host:repo_port add set name="info.keywords" value="Security Update" Go to the Available Updates View and check that there is a star in the Security Column for the package	updatetool highlights Security Updates in the Available Updates View
UC21.SecurityUpdate.F008	Check that Available Updates are displayed first in the Available Updates View	install updatetool from an architecture specific image modify defaults.cfg by setting the following attributes : _security_update_attr = info.keywords and _security_update_keywords = Security Update in the main part of defaults.cfg file Start updatetool Start a testing repo and publish 4 test packages : foo1@1.0-1.0, foo2@1.0-1.0, foo3@1.0-1.0 and foo4@1.0-1.0 Using updatetool, create a user image for the testing repository and install the available packages publish an update for foo1 (foo1@1.0-2.0) and foo2 (foo2@1.0-2.0) without setting the info.keyword attribute publish an update for foo3 (foo3@1.0-2.0) and foo4 (foo4@1.0-2.0) and set for those updates the info.keywords to "Security Update", this is achieved by the command : pkgsend -s http://repo_host:repo_port add set name="info.keywords" value="Security Update" Go to the Available Updates View and check that there is a star in the Security Column for the packages foo3 and foo4 and that they are listed first in this View before foo1 and foo2 updates	updatetool highlights Security Updates in the Available Updates View in the Top order
UC21.SecurityUpdate.F009	Check that Available Add-ons View does not contain * for packages having Security attribute set	to a test repository, publish a test package foo1@1.0-1.0 and set the info.keyword attribute to "Security Update" Publish a second package foo2@1.0-1.0 without setting the info.keyword attribute Publish an update for foo2 (foo2@1.0-2.0) In updatetool, create a user image for this repo Check that the Available Add-ons view does not highlight the Security icon (star) for those packages
UC21.SecurityUpdate.F010	Check that the updatetool highlight the presence of security updates if at least one update level is considered as seurity update	on a testing repo, publish a test package Create a user image and install this package Publish a first update without setting the info.keywords attribute publish a second update by setting the info.keywords to a value matching the configuration in defaults.cfg Publish a third update without setting the info.keywords attribute	Check that the updatetool highlights the presence of a security update for this package
UC21.SecurityUpdate.F011	Check that the updatetool does not highlight as security update an update for a package where the info.keywords attribute value does not match what is in defaults.cfg	Start a test repo Publish a package to tis repo Create a user image using updatetool and install this package publish an update for this package and set the info.keywords attribute to "Security"	Check that the updatetool does not highlight this update as a Security Update
UC21.SecurityUpdate.F012	Check that SW Update Manager highlights User Images having Security Updates	Create a User image with a repo where some packages have Security Updates available Create a Lower versions of such packages Launch SW Update Manager using the notifier or manually Check that the Security Icon is displayed for User Images having packages with Security Updates	The Security Icon is displayed for User Images having pending Security Updates
UC21.SecurityUpdate.F013	Check that SW Update Manager allows to Apply Security Updates successfully	Create a User image with a repo where some packages have Security Updates available Create a Lower versions of such packages Launch SW Update Manager using the notifier or manually Check that the Security Icon is displayed for User Images having packages with Security Updates Apply those updates	Applying Security Updates using SW Update Manager should be successful