Component / Release
TC01: Add a component and release with vendor present
| Step | Action | Result |
|---|---|---|
| 1 | Sign In with a known user | User successfully signed in and Home page is displayed |
| 2 | Click Components tab | Components page is displayed |
| 3 | Click Add Component button | - New Component page is displayed with mandatory fields marked with red star: Name, Categories, Component Type. - A message Success:New Component is displayed |
| 4 | Fill in a component Name, Categories and Component Type fields. Eg: - Name: Component 1@1 - Categories: Categories_1@1 - Component Type: OSS | Values are entered in the fields |
| 5 | Click Create Component button | - Create component successfully. - Redirect to the edit component page. -Show message: Success:You are editing the original document. |
| 6 | Click Releases tab Click Add Release button | Redirect to Add Release page |
| 7 | Fill in a release Version and CPE ID Eg: - Version: version1.0.0.x - CPE ID: UUID_1002 | Values are entered in the fields: - Version: version1.0.0.x - CPE ID: UUID_1002 |
| 8 | Click Create Release button | - Create a release successfully. - Redirect to the edit new release page. - The message Success:You are editing the original document. is displayed |
| 9 | Click Vendor field | Search Vendor dialog is displayed |
| 10 | Click Add Vendor button | Create new Vendor dialog display |
| 11 | Input data in fields - Full Name: add vendor 01 -Short Name: add vendor01 -URL: https://github.com/eclipse-sw360/sw360 | Values are entered in the fields. |
| 12 | Click Add Vendor button | The vendor is added in Vendor field of the release with full name is add vendor 01 |
| 13 | Click Attachments tab | Attachments page is displayed |
| 14 | Click Add Attachment button | Upload Attachment dialog is displayed |
| 15 | Click Browse and select the attachment. Eg: attachment1.xlsx | File name is displayed in the dialog |
| 16 | Click Upload button | The file is uploaded and dialog is closed. Also the attached file is listed in the Attachment page |
| 17 | Change the attachment Type to real type. Eg: Component license information (Combined) | Type changed successfully |
| 18 | Click Update Release button | Message: Success:Release {name} ({version}) updated successfully! is displayed |
TC02: Verify data after add a component and release with vendor present
| Step | Action | Result |
|---|---|---|
| 1 | Search for the component is created in TC01: - Click Components portlet - At Advanced Search area, input Component 1@1 in the Component Name textbox. - Click Search button | The new component display in the table with: - Vendor: add vendor01 - Component Name: Component 1@1 is displayed with hyper link. - Main licenses: blank - Component Type: OSS |
| 2 | Click hyper link of name Component 1@1 | Redirect to view component Component 1@1 page |
| 3 | Click Release Overview tab | The release display with: - Name: Component 1@1 - Version displays with hyper link: version1.0.0.x - Clearing State: New - Clearing Report: no report - Release Mainline State: Open |
| 4 | Click hyper link version1.0.0.x | Redirect to view screen of release Component 1@1 version1.0.0.x Data of the release: - Summary tab: + display text with: COMPONENT 1@1 VERSION1.0.0.X + CPE ID: UUID_1002 + Created on: date of created. + Created by: user created. + Modified On: date of modified. + Modified By: user modified. + Clearing State: New + Release Mainline State: Open + Release Vendor with: Full Name: add vendor 01 Short Name: add vendor01 URL: https://github.com/eclipse-sw360/sw360 |
| 5 | Click Attachments tab | Display file name attachment1.xlsx in the table. |
TC03: Modify a component and release with vendor present
| Step | Action | Result |
|---|---|---|
| 1 | Search for an existing component (e.g. created in TC01: Component 1@1) and click Edit icon | Success:You are editing the original document message is displayed |
| 2 | Click Releases tab | Release list is displayed |
| 3 | Click Add Release button | Redirect to Add Release page |
| 4 | Fill in a release Version and CPE ID Eg: - Version: v1.0.0.1 - CPE ID: cpe:id:123456 | Values are entered in the fields: - Version: v1.0.0.1 - CPE ID: cpe:id:123456 |
| 5 | Click Create Release button | - Redirect to the edit new release page. - The message Success:You are editing the original document. is displayed |
| 6 | Click Vendor field | Search Vendor dialog is displayed |
| 7 | Click Search button. Select a vendor (eg: select vendor with full name VendorUp) Click Select Vendor button. | Dialog is closed and selected Vendor is added under Vendor field: VendorUp |
| 8 | Click Attachments tab Click Add Attachment button Click Browse and select the attachment. Eg: attachment2.img Click Upload button | The file is uploaded and dialog is closed. Also the attached file is listed in the Attachment page |
| 9 | Click Update Release button | Message Success:Release Component 1@1 (v1.0.0.1) updated successfully! is displayed |
TC04: Verify data after modify a component and release with vendor present
| Step | Action | Result |
|---|---|---|
| 1 | Continue TC03 | |
| 2 | Click Summary tab | Data in the tab: - Modified On: date of modified. - Modified By: user modified. Data of other fields in the tab is same data before updated. |
| 3 | Click Release Overview tab | New release with version v1.0.0.1 is added in the release table. |
| 4 | Click v1.0.0.1 hyper link | Text display with: COMPONENT 1@1 V1.0.0.1 at the right corner. - At Summary tab: + CPE ID: cpe:id:123456 + Release Vendor: display with Full Name, Short Name and URL correctly with vendor VendorUp - At Attachments tab: attachment attachment2.img display in the attachment table with correct information. |
| 5 | Click Component 1@1 hyper link | Redirect to view screen of Component 1@1 component. |
| 6 | Click Attachments tab | Data in the tab is same data before updated. |
| 7 | Click Vulnerabilities tab | Data in the tab is same data before updated. |
TC05: Add and modify a component and release with all fields filled in
| Step | Action | Result |
|---|---|---|
| 1 | Click Components tab Click Add Component button Fill in all editable fields Click Create Component button | - Redirect to edit component screen with the message Success:You are editing the original document. is displayed in the left corner. - Create component successfully. Data match with input data. |
| 2 | Click Releases tab. Click Add Releases button. At Summary tab, fill in all editable fields under Release Summary and Release Repository. Click Create Release button. | Redirect to edit release screen. Created release successfully. Data match with input data. |
| 3 | Click Linked Releases tab Click Click to add Releases button | The dialog Link Releases is displayed. |
| 4 | Input search name into textbox Click Search button Select 3 releases. Click Link Releases button | Dialog is closed and selected release is displayed under Linked Releases section. |
| 5 | Click Linked Packages tab Click Add Packages button | The dialog Link Packages is displayed. |
| 6 | Input an exist orphan package name into textbox. Click Search button. Select a package. Click Link Packages button. | Dialog is closed and selected package is displayed under Linked Packages table |
| 7 | Click Clearing Details tab Fill in all editable fields | Values are entered in the fields |
| 8 | Click ECC Details tab Fill in all editable fields | Values are entered in the fields |
| 9 | Click Attachments tab Click Add Attachment button Click Browse and select the attachment. Eg: attachment3.xlsx Click Upload button | The file is uploaded and dialog is closed. Also the attached file is listed in the Attachment page |
| 10 | Click Update Release button | - Success:Release {componentName} ({version}) updated successfully! message is displayed. - Redirect to the view release screen. |
| 11 | Check all fields of the release by click tabs: Summary, Linked Releases, Linked Packages, Clearing Details and Attachments. | Values are filled in correctly, match with input data. |
| 12 | Click Edit Release button, modify some fields. Eg: - Version field ( in Summary tab): rename version name_updated - ECC Status field (in ECC Details tab): Approved. Click Update Release button. | Values are updated successfully |
TC06: Delete a component that is first linked to a project and then not, and a project
| Step | Action | Result |
|---|---|---|
| 1 | Create a new component Eg: component with name Component @1234 | Component is created successfully |
| 2 | Add a new release to this component Eg: release Rel1 | Release is added successfully |
| 3 | Create a new project P1 | Project is created successfully |
| 4 | Add the linked release Rel1 to project P1. | Release linked successfully |
| 5 | Click Components portlet. Search component Component @1234 by name at advanced search. | Component Component @1234 display on the result table. |
| 6 | Click delete icon of component Component @1234 | A warning The component Component @1234 cannot be deleted, since it contains 1 releases. Please delete the releases first. |
| 7 | Click OK button in the warning dialog. | The dialog is closed, component is not deleted |
| 8 | Click Components portlet. Search for the component Component @1234 and click hyper link of component Component @1234. | View screen of Component @1234 component is display |
| 9 | Click Release Overview. Click Delete icon button of release Rel1. Click Delete Release button in the dialog. | - Dialog Delete Releases is displayed. - Delete the release is failure. - The message: I could not delete the release, since it is used by another component (release) or project display. |
| 10 | Go to project P1, delete project P1. | The project is deleted successfully |
| 11 | Go to component Component @1234, at Release Overview tab, click Delete icon button of release Rel1. | Show message: Do you really want to delete the release {componentName} ({version}) ? |
| 12 | Click Delete Release button | Release is deleted successfully |
| 13 | Click Edit Component button. Click Delete Component button. | The dialog is displayed with message: Do you really want to delete the component {componentName} ? |
| 14 | Click Delete Component button | Component is deleted successfully |
TC07: Add new attachments to an existing release and delete attachments
| Step | Action | Result |
|---|---|---|
| 1 | Search for an existing component (e.g. created in TC01) and click Release Overview tab | The list of releases are displayed |
| 2 | Click edit icon in the Action column of release version that needs a new attachment. Eg: release Rel1. | Edit release Rel1 page is displayed. |
| 3 | Click Attachments tab Click Add Attachment button Click Browse and select several attachments. Eg: 5 attachment files (att1, att2, att3, att4, att5) | File names are displayed in the dialog |
| 4 | Click Delete button near some files not to be added. Eg: delete 2 attachment files (att1, att3) | File names are removed from the list |
| 5 | Click Upload button for the remaining files. | The attached file are listed in the Attachment page: att2, att4, att5 |
| 6 | Change some Attachment type to real type, e.g. source file, clearing report, CLI,… | Type changed successfully |
| 7 | Click Update Release button | Release Ree1 is updated correctly. |
| 8 | Click Edit Release button | Success:You are editing the original document. message is displayed |
| 9 | Click Attachments tab | Attachments page is displayed |
| 10 | Click delete icon to delete an attachment | Show message: Do you really want to delete attachment {attachmentName}({attachmentId})? |
| 11 | Click Delete Attachment button | Attachment is deleted successfully, data of attachment is removed from attachment table. |
| 12 | Click Update Release button | Release Ree1 is updated correctly with message Success: Release {componentName}({version}) updated successfully! |
TC08: Duplicate an existing release
| Step | Action | Result |
|---|---|---|
| 1 | Search for an existing component with release with all fields filled in (Eg: created in TC05) and click Release Overview | The list of releases are displayed |
| 2 | Click Duplicate button under Action column | The page changes to create duplicate release screen |
| 3 | Check all fields from copied release | - Summary tab: + CPE ID field: blank + Remain fields are unchanged (exclude disable fields). - Linked Releases tab: there is no linked release. |
| 4 | Change the Version field and fill in a CPE ID. Eg: Version: ver_duplicate CPE ID: CPE ID_duplicate Click Create Release button | - Redirect to edit release screen. - Create duplicate release is success with message: Success:You are editing the original document. - Data of duplicate release is correct. |
| 5 | Modify some other fields. Eg: Release Date: 2023-06-12. Click Clearing Details tab | Clearing Details page is displayed and does not contain any field from copied release |
| 6 | Click Update Release button | The release is updated successfully with data correctly |
| 7 | Click component name link on top of the page | Summary page for the component is displayed |
| 8 | Click Release Overview tab | The new copied release is listed among previous releases |
TC09: Search for and create a new vendor for a new release
| Step | Action | Result |
|---|---|---|
| 1 | Click Components portlet At advanced Search, search for an existing component. Eg: input Comp1 in the Component Name text box. Click Search button. | Component Comp1 display in the result table. |
| 2 | Click edit icon in Actions column of component Comp1. | Edit screen of component Comp1 is displayed with message: Success:You are editing the original document |
| 3 | Click Releases tab Click Add Releases button | The page changes to New Release Edit page |
| 4 | Fill in a release Version and CPE ID Eg: + Version: @1.0.2 + CPE ID: moshiano_002 | Values are entered in the fields |
| 5 | Click Vendor field | Search Vendor dialog is displayed |
| 6 | Click Add Vendor | Create New Vendor dialog is displayed |
| 7 | Fill in Full name, Short name and URL Eg: Full Name: Fullvendor_0909 Short Name: Short_ven090 URL: https://github.com/ | Values are entered in the fields |
| 8 | Click Add Vendor | Dialog closes and the new vendor is displayed in release Vendor field with full name Fullvendor_0909 |
| 9 | Click Create Release | Redirect to edit release page with the message Success:You are editing the original document. is displayed |
| 10 | Click component name link on top of the page | Summary page for the component is displayed. The new vendor for the new release, as well as existing vendors from previous releases are listed under Vendors field for the component |
TC10: Link a release to the project in view component page and check used by projects
| Step | Action | Result |
|---|---|---|
| 1 | Search for an existing component with release and click Release Overview tab | The list of releases are displayed |
| 2 | Click Link Project button under Action column | The dialog Link Release to Project is displayed with Link to Project button is disabled |
| 3 | Click Search button then choose a project to link | Link to Project button on the dialog is enabled |
| 4 | Click Link to Project button | The release {component name} ({version}) has been successfully linked to project {project name} Click here to edit the release relation as well as the project mainline state in the project. message is displayed |
| 5 | Click here hyperlink in the dialog | Redirect to the edit project page with the release was linked (displayed on License Clearing page) |
| 6 | Re-open the release at view page and click Summary tab | Used by project information is updated correspondingly |
TC11: Link a release to a project in the view release page
| Step | Action | Result |
|---|---|---|
| 1 | Search for an existing component with release and click Release Overview tab | The list of releases are displayed |
| 2 | Click a release name hyperlink. Eg: release R1 | Redirect to the view release page |
| 3 | Click Link to Project button | The dialog Link Release to Project is displayed with Link to Project button is disabled |
| 4 | Click Search button then choose a project to link | Link to Project button on the dialog is enabled |
| 5 | Click Link to Project button | The release {component name} ({version}) has been successfully linked to project {project name} Click here to edit the release relation as well as the project mainline state in the project. message is displayed |
| 6 | Click here hyperlink in the dialog | Redirect to the edit project page with the release was linked (displayed on License Clearing page) |
TC12: Import a new component by .spdx/.xml/ .rdf file
| Step | Action | Result |
|---|---|---|
| 1 | Click Components tab | Components page is displayed |
| 2 | Click Import SBOM button | A dialog Upload SBOM is displayed |
| 3 | Choose a .spdx or .xml or .rdf file by clicking on the Browse button or drop/draft a file into the dialog | The message is displayed in the dialog: The new Component and new Release will be created, do you want to import? New Component: {new component names} New Release: {new release names} |
| 4 | Click Import button | The dialog is closed. New releases and new components are imported successfully |
TC13: Export components without releases
| Step | Action | Result |
|---|---|---|
| 1 | Click Components tab | Components page is displayed |
| 2 | Click Export Spreadsheet button and choose Components only option | - A new file with name’s format components-{yyyy}-{mm}-{dd}.xlsx is downloaded - The content of the downloaded file includes information of all components in the system |
TC14: Export components with releases
| Step | Action | Result |
|---|---|---|
| 1 | Click Components tab | Components page is displayed |
| 2 | Click Export Spreadsheet button and choose Components with releases option | - New file with name components-{yyyy}-{mm}-{dd}.xlsx is downloaded. - The content of the downloaded file includes information of all components and releases in the system |
TC15: Create a clearing request for a release
| Step | Action | Result |
|---|---|---|
| 1 | Search for an existing component with releases and click Release Overview tab | The list of releases are displayed |
| 2 | Click Edit button under Action column. Eg: edit release R1 | Redirect to view release page and the message Success:You are editing the original document. is displayed |
| 3 | Click Attachments tab, then add a source file (Eg: .rdf file) with Type is Source file | The data is updated correspondingly |
| 4 | Click Update Release button | The message Success:Release {release name} updated successfully! is displayed |
| 5 | Click Clearing details tab, then click Fossology Process icon beside Clearing State field and wait for the process to finish | The message The FOSSology process already finished. You should find the resulting report as attachment at this release. is displayed in the Fossology Process dialog |
| 6 | Click Close button in the dialog | The dialog is closed |
| 7 | Reload this page, then click Attachments tab | A new file is listed in Attachments page with name’s format {component name}-{version}-{yyyymmdd}-{hhmm}-SPDX.rdf |
Last modified March 1, 2024: feat(docs): Update test case for Component, Release (d3f2afc)