Test Plan In Alm | How To Create Test Resources

How to Upload Tests using Microsoft Excel

Step 1) Before uploading the tests from excel, we need to prepare the Excel such that it can be uploaded.

Select the Fields that you wish to upload into ALM and create a header in Excel for those fields.
Enter a valid data in each one of those fields as shown below.

Step 2) After selecting the data to upload, click ‘Export to HP ALM’ from ‘Add-Ins’.

Step 3) The ALM Export Wizard opens. Enter the HP ALM Server URL and Click ‘Next’.

Step 4) Enter the user name and password for authentication and Click ‘Next’.

Step 5) Select the Domain, Project Name into which we would like to upload the tests and Click ‘Next’.

Step 6) Select the type of data that we would like to upload. In this case, it is tests. We will also upload Defects in the upcoming chapters.

Step 7) Enter the New Map name. The first option, ‘Select a map’ is disabled because we haven’t created a map so far. Hence we should create new map name and click ‘Next’. We haven’t selected ‘Create a Temporary map’ as we would like to reuse every time for uploading ‘tests.

Step 8) Upon Clicking ‘Next’, the mapping dialog opens as shown below.

The left pane grid items that are listed correspond to the fields that are available for upload in HP ALM. Please note that the fields marked in ‘RED’ should be mapped as they are mandatory fields.
The right pane grid items refer to the fields that are mapped so that values in Excel will flow into those corresponding fields of ALM.

Step 9) Now let us understand how to map the fields in Excel against the fields in ALM.

Select the Field that user would like to map and click on the arrow button as shown below.

Enter the column name in Excel that corresponds to the appropriate column name in HP ALM.

Map all the required columns in Excel against the appropriate fields in HP ALM. After mapping all the required fields, click ‘Export’.

Step 10) Upon successful upload, ALM displays the message as shown below. If errors appear please fix the issue and try re-uploading the same.

Some of the common errors are listed below :

The Subject/Path is invalid/unavailable or NOT mapped by the user.
The Field ‘Test Type’ has a value other than Manual. Automated tests CANNOT be uploaded using Excel.
Test Name field is Empty or NOT Mapped.
Status shouldn’t have values other than Design, ready, Imported, Repair.

Step 11) Now let us verify the same under ‘Tests’ Tab. All the test details are uploaded as shown below.

Note : Users can also perform re-uploading of tests. In case of re-uploading the test cases, if the test name already exists and if there is just a change in step description then the test will be overwritten with the existing one. If the test name is different from the uploaded one, it uploads as a new test.

Conclusion

The test plan module in HP ALM is used for planning, organizing, and managing your testing efforts.
With the Test Plan module, you can create test plans, test cases, and test sets, and assign them to specific releases and cycles.
The Test Plan module provides advanced reporting and analysis capabilities, allowing you to generate custom reports and dashboards based on your testing data and metrics, and gain insights into your testing quality and performance.
By utilizing the Test Plan module in HP ALM, you can streamline your testing processes, increase collaboration and communication among your testing team, and ultimately deliver high-quality software products that meet the needs of your stakeholders.

Plan and run test suites

After you create a test suite, you can plan how to run it. This topic describes how to plan and run a test suite.

HP ALM - Create Test Case in Test Plan — HP ALM – Create Test Case in Test Plan

How to Plan Tests in ALM

Here are the steps to be followed so that we can effectively plan and execute tests using ALM.

Define the testing scope:Identify the specific features, functionalities, and components that need to be tested.
Determine the testing objectives:Establish what the testing aims to achieve, such as validating system requirements, ensuring system performance, and detecting defects.
Create a test plan:Develop a detailed document that outlines the testing strategy, approach, and methodologies to be used.
Identify the test cases:Identify the individual test cases that will be executed during testing. These test cases should align with the testing objectives and scope.
Define the testing environment:Define the hardware, software, and network configurations required to execute the tests.
Establish testing resources:Identify the people, tools, and equipment needed to conduct testing.
Assign roles and responsibilities:Assign specific roles and responsibilities to team members for executing the tests, recording results, and reporting defects.
Set testing timelines:Establish the testing schedule and milestones, including the start and end dates, testing phases, and deliverables.
Execute tests:Perform the identified test cases according to the test plan and record the results.
Report and manage defects:Log any defects discovered during testing and manage the resolution process.
Analyze testing results:Analyze the testing results to identify trends, patterns, and areas for improvement.
Update the test plan:Update the test plan based on the testing results, feedback, and lessons learned.

Enforce manual test run order

When planning a run of a test suite containing manual tests, you can set the suite run to enforce the run order of the manual tests in the suite. This means that a manual test run cannot be executed until the preceding manual test runs in the suite have been completed.

Note: Enforcing test run order is not supported for automated tests. In a suite containing both automated and manual tests, the automated tests can be run at any time, and their run status is ignored when enforcing the run order of manual tests in the suite.

To enforce test run order for a suite run, do one of the following:

Before creating the suite run, select the Details tab of the test suite and set the Enforce order for manual field to Yes.

The value you set at the test suite level is the default for all future suite runs planned for the suite.
When creating the suite run, set the Enforce order for manual field for the suite run to Yes. For details, see Plan a test suite run.

Note: After a suite run has been created, the Enforce order for manual field becomes read-only and cannot be changed.

When is a test run considered completed?

By default, a test run is considered completed when its status is Passed, Failed, or Skipped. The administrator can choose which statuses are considered completed, by modifying the relevant business rule for the Manual Run entity. For details, see Business rules.

Tip: The administrator can define a business rule to automatically notify the assigned tester when the next test is ready to run. For details, see Notify the assigned tester when a test is ready to run.

If a test run in the suite was completed, and its run status was then changed back to Planned after subsequent tests were already allowed to run, the updated status affects all subsequent test runs. This means that all test runs after the run marked Planned cannot be executed.

Example: A suite contains 5 manual test runs. Test runs 1, 2, and 3 were passed. Test run 4 can currently be executed.

Run order	Status	Blocked by previous run	Can be executed
Test run 1	Passed	No	Yes
Test run 2	Passed	No	Yes
Test run 3	Passed	No	Yes
Test run 4	Planned	No	Yes
Test run 5	Planned	Yes	No

Then, Test run 2 is updated from Passed to Planned. Now, Test runs 3 and 4 cannot be executed.

Run order	Status	Blocked by previous run	Can be executed
Test run 1	Passed	No	Yes
Test run 2	Planned	No	Yes
Test run 3	Passed	Yes	No
Test run 4	Planned	Yes	No
Test run 5	Planned	Yes	No

To override this restriction and allow subsequent tests to run, you can manually change the Is completed field to Yes for each of the test runs before the run you want to execute.

HP ALM - Adding Test Cases to Test Sets — HP ALM – Adding Test Cases to Test Sets

View the suite run results

When the suite’s tests run, ALM Octane compiles the run results into a single report.

To view the suite run results:

In the test suite, click the Suite Runs tab.
In the list of suite runs, click the link for the suite run you want to view.
In the suite run instance, click the Runs tab. ALM Octane displays the list of all runs.
In the suite run, click the Report tab. The suite run report is displayed.

Tip: To view the test run details, click the test run ID.
In the View by box (top right), select how to view the results:
- Tests: to show the results per tests
- Order: to show the results in the order of the runs
Scroll or click the links to view each test in the suite, as well as the specific steps in each test.

The report page also shows the phase each test was in when the run was created.

How to Execute Tests

Step 1) Created test sets are now ready for execution. Tests can be executed using two options.

Run Test Set – This option allows user to execute all the tests in a selected test set.
Run – This option helps user to execute just the selected test.

Step 2) Let us execute the entire test suite of the Login module by selecting ‘Run Test Set’ option. Upon clicking ‘Run Test set’ it displays the user with two options.

Manual Runner (default) – The order of the tests displayed during the execution would be as that of the order that is displayed in the test set grid.
Automatic Runner – The order of the tests displayed during execution would be shown as that of the order set in the execution flow tab.

Let us proceed with the default option.

Step 3) The Manual Test runner is displayed to the User. In this Dialog let us understand the important features.

Begin Run – Helps to kick start the execution
End Run – Terminates the current Execution and closes the manual runner.
Cancel Run – Cancels the execution of the current tests.
Attachments – Helps us to attach screenshot/any other information related to the this test execution
New Defect – Upon clicking on it new defects dialog opens using which a Defect can be posted.
OS Info – Gives information about the operating system in which the tests are executed.
Run Name – Unique Time stamp using which the test results can be analyzed at later point in time.

Click ‘Begin Run’.

Step 4) Manual test runner with test controls and steps are displayed to the user. Let us understand the functionalities available in this test runner dialog.

Step Numbers created during test design stage
Description of the selected step.
Expected Result of the selected step.

Step 5) Thenext test in the test set will be displayed to the user. Repeat Step 3 and Step 4 to execute the test and mark the status accordingly.

HP ALM - Import Test Cases From Excel — HP ALM – Import Test Cases From Excel

How to create Test Resources

The Test Resources enables users to manage resources that are usually picked up by automated/performance tests. Users can upload the script which can be used by one or more tests. They can also be downloaded/edited and uploaded back again into test resources.

Let us see how we can make use of Test Resources module effectively. This module is demonstrated by uploading the same excel file into test resources that we used for importing the tests from excel into ALM.

Upload of Test Case excel is recommended so that we can edit the tests whenever required and re-upload only the modified test cases. It is also easy to add new tests and upload just the newly added tests.

However we can also upload other types of files such as .xls, .vbs, .qfl etc.

Step 1) Navigate to Test Resources module as shown below. The test resources module page opens.

Step 2) Create a ‘New Folder’ by clicking on New Folder Icon as shown below. The New folder dialog opens. Let us create test resource for all three tests viz – Manual, Automation and Performance.

Step 3) The folder is created as shown below.

Step 4) Similarly let us create two more folders viz – Automation and Performance. After Creating a folder for each one of the test resources, the final folder structure will be as shown below:

Step 5) Let us create a New test resource by uploading the excel file that we have created for writing manual tests which were uploaded into ALM. Select the folder where user would like to upload the test resource.

Step 6) Enter the name of the test resource and also select the type of the resource and click ‘OK’.

Step 7) Upon creating the test resource, now we need to upload the resource so that it is available under ‘Resource Viewer’ Tab which will be used across tests.

Click ‘Resource Viewer’ Tab
Click ‘Upload File’ and select the file for upload

Step 8) After uploading the file, the Status will be shown to the user and it will be available for download.

Note: The Following types of Test Resources are uploaded that can be used for executing the automated tests.

DataTable
Environmental Variables
Function Libraries
Recovery Scenarios
Shared Object Repository

Video on Test Plan

Click here if the video is not accessible

key takeaways:-

You will use the Test Plan module in QualityCenter to design and create your test cases/scripts.
You can link your Tests in Test Plan Module with Requirements in the Requirement Module for easy tracking.
QualityCenter provides many a features like copying test steps , emailing scripts for review , adding attachments etc. to facilitate faster development of test cases.

Test Plan Module in HP ALM (Quality Center) Tutorial – Phần 3

Bài đăng này đã không được cập nhật trong 4 năm

Tiếp phần: Làm thế nào để upload Tests sử dụng Microsoft Excel

Bước 11) Tất cả Test details được tải lên như dưới đây

Người dùng có thể thực hiện tải các test cases lên. Trong trường hợp tải lại test cases, nếu tên đã tồn tại và nếu có bất kỳ thay đổi nào thì sẽ ghi đè lên cái đã có sẵn, nếu tên giống nhau thì chỉ upload một file còn tên khác nhau thì upload như là một file mới.

Run a test suite

A test suite runs as a collection of test runs.

By default, all the tests included in the test suite are run unless certain tests were excluded in the planning stage.

Note: When a test suite runs, the included test runs are created in draft mode. The “Alert user” business rules that govern test runs creation are ignored.

You can prevent creating test runs in draft mode by setting the IGNORE_ALERT_RULE_WHEN_CREATE_IN_DRAFT_MODE parameter to false. As a result, the “Alert user” business rules are triggered, and the runs cannot be created as drafts. When a test suite runs, an error occurs.

For details, see Configuration parameters.

To run a test suite:

On the test suite Planning tab, verify that the necessary tests are included in the run.

To change the tests included in the run, in the Include in next run column, toggle the tests to run. Note that check boxes next to the test ID do not mark the tests to run.
Click Run Suite . The Run

dialog box opens.
Verify the settings and click Let’s Run.

The Manual Runner window opens. For details, see Run manual and Gherkin tests.

The status of the test suite is automatically updated according to the status of the test runs.

Note: The final status of the test suite follows ALM Octane’s business rule logic. The business rules run sequentially and the final status is dictated by the last rule. For example, the first built-in business rule sets the test suite status to Passed, if a test suite’s tests were either Skipped or Passed. However, a subsequent rule whose criteria is to look for any Skipped tests, resets the status of the test suite to Skipped. The business rules and their order are set by the admin. For details, see Business rules.

HP ALM - Organize Test Cases — HP ALM – Organize Test Cases

View additional details on suite runs

For automated tests, the right pane of the Suite Run > Runs tab provides additional information:

The Preview tab shows general information on the test run: Name, description, release assignment, and comments.
The Report tab provides a test run report after the run is executed. If there is an error, you will see the related stack trace information.
The Test Runners tab shows details of the related test runners: Framework, CI server, job name, and build number. Click a test runner to filter its related test runs.

When you run a suite, the test runner’s status changes to Initializing, In Progress, and Finished. Click the toolbar refresh button to see the status changes. The tab also provides a link to access the test runner execution log.

For details on configuring test runners, see Trigger on-demand automated test runs.

How to Analyze Test Result

Step 1) Once the test execution is done, testers can view the results in the “Test Runs” module. It contains the results of test instance runs and test set runs.

Goto “Test Runs” in “Testing” Tab and the window opens as shown below:
The Run Name is a unique value generated for each one of those test executions.
‘Status’ shows the final status of the test execution.

The detailed Result can be viewed by clicking on the ‘Run ID’.

Step 2) The Run details dialog opens up and user will be able to view the detailed result.

Goto ‘Report’ tab of the ‘Run Details’ window.
Testers can check the status of each one of those test steps.
Click ‘Ok’ to close the dialog.

Video on Test Lab

Click here if the video is not accessible

points to remember:

You will use the Test Lab module in QualityCenter to execute your test cases
Before you begin execution , you need to create a “Test Set Tree”
To create a Test Set Tree , you need to first create a “Test Set Folder”
Next, you will add “Tests” created in the Test Plan Module, to your Test Set Folder.
A Test Set Folder together with added Tests is called the Test Set Tree (since it looks like a tree structure.)
Test sets can include both manual and automated Test .
You can include the same Test in different Test Sets or add multiple instances of a Test to the same Test Set.
Quality Center also provides for scheduling where in you can specify the date and time of execution of your Test Sets.

Test Plan Modules in HP ALM

HP ALM - Test Plan - Graphs — HP ALM – Test Plan – Graphs

How to Create Test Plan

Step 1 ) Similar to requirements, let us create a placeholder/folder for each one of the test types such as Functional and Non Functional.

Click on Test Plan link from the ALM Home page
Click ‘New Folder’ Icon
Enter the Folder Name as ‘Functional’ and click ‘OK’

Step 2) The created folder would be displayed as shown below.

Step 3) Similarly let us creates subfolders for ‘Manual’ and ‘Automated’ Tests under ‘Functional’ Folder. Hence the Final Folder Structure will be as shown below:

Note: We will NOT be able to create automated test scripts/Performance test scripts from ALM; instead it has to be created from respective HP tools such as UFT for functional and Load runner for performance. It is then saved into ALM so that they can be scheduled, executed, monitored and reported.

Step 4) It would be better to create a New folder for each one of the modules of the application so that we don’t dump all manual tests in one folder. For Complex applications there would be thousands of tests which would be difficult to handle if they are not aligned properly.

Step 5) Now Let us create a Manual Test for the ‘Login’ Module by clicking on the ‘New Test’ Icon in ‘Test Plan’ Tab.

Step 6) Enter the following details for creating the new test successfully.

Enter the New test Name
Enter the Type of the Test. In this case it is ‘Manual’ Test.
User can also enter other non-mandatory fields such as date, Description as shown below.
Click ‘Submit’ once all the details are entered.

Step 7) Once the test is created, the created test will appear under the ‘Manual’ tests folder with other tabs generated as shown below. Let us discuss each one of these tabs in details in upcoming steps.

Step 8) Click ‘Design Steps’ tab and click on ‘New Step’ icon as shown below. The Design step details dialog box opens

Enter the Step Name
Enter the Step Description
Enter the Expected Result
Click ‘OK’

Step 9) Repeat the Step#6 and enter all the relevant steps to test the functionality. After creating all the required steps, ‘Design Steps’ tab displays all the created steps as shown below.

Step 10) Parameters, helps the user to assign a value to a variable that allows the user to execute the same test with different sets of data. In this case, the user name and password can be two parameters which would be assigned with a value. We will understand the importance of having parameters while test execution which will be dealt in Test Lab module.

Now, Let us see how to create parameters.

Select the test step against which we would like to add the parameter.
The ‘Parameter’ Icon will be enabled. Click on the same as shown below.

Step 11) The Parameter dialog will open as shown below. Click on ‘New Parameter’ button.

Step 12) The test parameter details dialog opens.

Enter the parameter name
Assign a Value to the Parameter
Click ‘OK’.

Step 13) The ‘parameters’ dialog is displayed back to the user

With the created variable
The value
Click ‘OK’.

Step 14) Now we can notice that the parameter is added in the ‘Test Step’ itself as shown below.

Repeat the same for password field as well.

Similarly, create parameter for Password Filed

Step 15) The created parameters can be viewed/edited in the parameters tab. This dialog also helps us to create, delete the parameters associated with the tests.

Step 16) The attachment tab allows the user to upload any type of file such as ‘xls’, ‘jpg’ etc.

Step 17) The test configuration helps us to reuse the test for different use case scenarios. Let us understand how to work with test configurations with an example. By default there is a test configuration that is specified as that of test name.

Note: We CANNOT delete the default test configuration but we can edit the same.

Step 18) Let us say the login functionality can be performed by three types of business users such as ‘helpdesk’, ‘manager’ and ‘cluster head’.

Let us rename the default test configuration to ‘helpdesk’ by editing the name field of the ‘Test Configuration’.

Step 19) Now let us add the other two more test configurations viz – manager and cluster head. Click ‘+’ icon under test configurations.

Step 20) The ‘New test Configuration’ dialog opens up.

Enter the Test configuration name
Enter other non-mandatory parameters such as ‘created by’ , ‘creation date’, ‘description’
Click ‘OK’.

Step 21) Repeat the same step as above to create one more test configuration for ‘cluster head’ and the entire test configuration will be displayed to the user as shown below. This will allow the testers to execute the same test individually against all the created configurations during test execution which will result in no rewriting of tests.

Test Configuration should NOT be confused with test parameters. Hence we should understand the difference between parameter and test configurations. The Parameters are used to create variable and assign values for a specific step (parameterizing the test) while test configuration is applicable for all the steps and generally used to test different business use cases/Workflow. During Execution users can change values of the created parameters while a Test Case is executed for the selected configuration.

For Example, An online bill payment Application, user can select the payment mode. In case of ‘Credit Card’ Payments, user can either select master card, visa or American express. Each one of those having its own customer reward points. In order to test it, we can design a test such that each one of them are added into test configurations to verify the reward points.

Step 22) The ‘Req Coverage’ Tab helps the testers to map the test against a particular requirement(s) which helps users to generate coverage and traceability.

Click on ‘Req Coverage’ Tab.
Select the ‘Requirement’ which should be mapped against this particular test case
Click ‘<=’ button to map the selected requirements against the test. We can also map multiple requirements against the same test.

Step 23) The Tab ‘Linked Defects’ shows empty as we haven’t executed any test/raised any Defect against the test case. This tab will be populated with the defect details if the defects are posted against the test case at the time of creating the defects.

Step 24) History tab shows the list of changes made over time against this particular test case right from time of creating the test.

Làm thế nào để tạo tài nguyên

Test resources cho phép người dùng quản lý tài nguyên thường được chọn bằng cách automated/performance tests. Người dùng có thể tải đoạn script có thể sử dụng bởi một hoặc nhiều cách kiểm tra. Họ có thể tải hoặc sửa và tải lại test resources

Làm thế nào để chúng ta có thể sử dụng Test Resources hiệu quả. Module này được thể hiện bằng cách tải lên cùng một tệp excel trong test resources mà chúng ta đã sử dụng cho importing các trường hợp kiểm thử từ excel vào ALM. Tải lên các trường hợp Tests để chúng tôi có thể chỉnh sửa bất cứ khi nào cần và chỉ tải lên lại các trường hợp kiểm tra đã sửa đổi. Nó cũng dễ dàng để thêm trường hợp mới và chỉ tải lên các trường hợp mới được thêm vào.

Tuy nhiên chúng ta có thể upload các loại file như .xls, .vbs, .qfl etc.

Bước 1) Điều hướng đến Test Resources như dưới đây. Trang test resources được mở

Bước 2) Tạo một thư mục ‘New Folder’ bằng cách nhấp vào icon New folder như dưới. Thư mục mới được mở.

Bước 3) Thư mục được tạo như dưới

Bước 4) Tương tự chúng ta tạo nhiều hơn 2 thư mục viz – Automation và Performance. Sau khi tạo một thư mục cho mỗi test resources, cấu trúc thư mục cuối cùng sẽ như dưới đây

Bước 5) Chúng ta hãy tạo một test resource bằng cách tải file excel mà chúng ta đã tạo bằng tay trong ALM. Chọn thư mục nơi người dùng muốn tải test resource.

Bước 6) Nhập tên của Test resource và cũng chọn type là test resource sau đó click ‘ OK’

Bước 7) Các bước cần tải resource

Nhấp vào ‘Resource Viewer’ Tab
Nhấp vào ‘Upload File’ và chọn file upload

Bước 8) Sau khi tải file, trạng thái sẽ được hiển thị tới người dùng và nó sẵn sàng để tải xuống.

HP ALM - Requirement - Test Case Linking or Test Coverage — HP ALM – Requirement – Test Case Linking or Test Coverage

Upload Test Plan from Excel

Let’s follow these steps to upload the test plan to ALM from Excel:

Open the Excel file that contains the data.
Organize the test plan data in the following columns:
- Test Plan ID
- Test Plan Name
- Description
- Start Date
- End Date
- Test Type
- Test Folder Path
- Test Status
- Test Priority
- Test Owner
- Comments
Save the Excel file in CSV format.
Open ALM and go to the Test Plan module and click on the “Import Test Plan” button.
In the “Import Test Plan” dialog box, select “CSV” as the file type and browse to the location where you saved the CSV file.
Map the fields from the Excel file to the corresponding fields in ALM.
Click on the “Import” button to upload the test plan data into ALM.
After the import is complete, review the test plan in ALM to ensure that all the data has been imported correctly.
Now execute the test plan in ALM and record the test results.

Làm thế nào để tạo một Test Set

Bước 1) Bước đầu tiên là để tạo một thư mục gốc để chứa một tập tests. Chúng ta có thể đặt tên cho nó phù hợp với bản phát hành và chu kỳ để dễ theo dõi.

Nhấp vào ‘Test Lab’ module dưới ‘Testing’ Tab
Tạo một tên một thư mục mới bởi nhấp vào ‘New Folder’ icon.
Hộp thoại ‘New Test Set Folder’. Nhập tên folder ‘2017 R1 – Cycle 1’.
CLick ‘OK’

Bước 2) Thư mục run sẽ được tạo như bên dưới

Bước 3) Chọn thư mục đã tạo và gán ‘Cycle’ cho nó, có nghĩa là toàn bộ tập test sẽ được thực hiện cho Cycle 1

Bước 4) Nhập tên của tập test và click ” OK”
Lưu ý: Trường Target Cycle bị vô hiệu hóa như vì ctarget cycle được chọn ở cấp thư mục(2017 R1 – Cycle 1).

Bước 5) Sau khi tạo một tập test, chúng ta cần chọn các thử nghiệm để thêm nó vào tập kiểm thử

Chọn tập Test
Điều hướng tới “Execution Grid”
Nhấp vào nút ‘Select Tests’. Cây Test Plan được mở
Chọn kiểm thử cần thực hiện cho chu trình hiện tại
Nhấp vào mút ‘<=’ để di chuyển các trường hợp kiểm thử từ test plan tới test lab.

Bước 6) Khi thêm Tests từ cây test plan, tất cả các tham số cấu hình của các tests đã chọn sẽ được hiển thị cho người dùng. Người dùng có thể chỉnh sửa cấu hình trước khi thêm nó vào test lab.

Lưu ý: Người dùng không có quyền kiểm soát lựa chọn cấu hình thử nghiệm trong Lab thử nghiệm. Do đó, toàn bộ cấu hình sẽ được thêm vào thử nghiệm theo mặc định. Trong trường hợp một trong các cấu hình được chọn KHÔNG phải là một phần của chu trình, sau khi thêm các trường hợp kiểm thử, hãy xóa khỏi test lab.

Bước 7) Sau khi chọn cấu hình, chọn các kiểm thử đã được thêm vào tập Test. Trong tường hợp này chúng ta có thể chọn tất cả 3 cấu hình; do đó chúng ta có thể tìm thấy 3 trường hợp của ’01- Login Test’.

Bước 8) Lặp lại các bước trên để tạo thêm cho tập test và chọn tất cả các thử nghiệm có liên quan được lên kế hoạch cho chu trình này. Sau khi tạo tất cả các tập test, cấu trúc của tập test sẽ như dưới đây

Bước 9) Tab quan trọng khác mà chúng ta cần hiểu là “Execution Flow”. Chọn ‘Excecution Flow Tab’ hiển thị thứ tự kiểm tra các trường hợp test trong khi thực hiện. Người dùng cũng có thể thay đổi thứ tự bằng cách sử dụng tab sẽ được xử lý trong một phần riêng biệt của mô-đun này.

Phần sau sẽ nói đến phần ” Làm thế nào để thực hiện test”

Tài liệu tham khảo : https://www.guru99.com/hp-alm-test-plan-module.html

Test Plan Module in HP ALM (Quality Center) Tutorial

Bài đăng này đã không được cập nhật trong 5 năm

Sau khi xác định yêu cầu xong đội phát triển bắt đầu thiết kế và thực hiện viết code chương trình, ở giai đoạn này đội kiểm thử cũng thực hiện viết kịch bản và có thể thực hiện test bản build đầu tiên

Thành công của bất kỳ sản phẩm nào đều phụ thuộc vào quy trình và chất lượng kiểm thử

Một kế hoạch kiểm thử tốt dẫn đến một sản phẩm ít lỗi

ALM hỗ trợ bảo trì và thực hiện các bài kiểm tra thủ công, tự động hóa và hiệu suất vì ALM được tích hợp hoàn hảo với tất cả các sản phẩm của HP như HP UFT và HP Load Runner.

Trong lần này chúng ta sẽ học các nội dung:

Làm thế nào để tạo Test Plan
Làm thế nào để tải Tests sử dụng Microsoft Excel
Làm thế nào để tạo tài nguyên Test

Bước 1) Tương tự requirements, nào bây giờ chúng ta sẽ tạo một placeholder/folder cho mỗi một loại test như Functional và Non Functional

Click vào Test Plan link từ trang chủ ALM
Click ‘New Folder’ Icon
Nhập tên thư mục như ‘Functional’ và click ‘OK’

Bước 2) Tạo thư mục sẽ hiển thị như dưới đây:

Bước 3) Tương tự, chúng ta hãy tạo các thư mục con cho ‘Manual’ và ‘Automated’ trong Thư mục ‘Functional’. Do đó, cấu trúc thư mục cuối cùng sẽ như dưới đây:

Bước 4) Tạo một thư mục cho mỗi modules của ứng dụng để lưu trữ tất cả manuals test trong một thư mục. Đối với các ứng dụng phức tạp sẽ có hàng ngàn kịch bản test do đó sẽ rất khó xử lý nếu chúng ta không sắp xếp quy củ. Một ví dụ tạo thư mục cha con như dưới đây.

Bước 5) Sau khi tạo xong thư mục Manual test thì bây giờ chúng ta sẽ tạo manual test cho module ‘Login’ bằng cách click vào ‘New Test’ icon trong ‘Test Plan’ Tab

Bước 6) Nhập chi tiết để việc tạo new test thành công

Nhập New test Name
Nhập loại Test. Trong trường hợp này nhập ‘Manual’ Test
Người dùng cũng có thể nhập các trường không bắt buộc khác như ngày, Mô tả như bên dưới.
Nhấp vào ‘Gửi’ khi tất cả các chi tiết được nhập.

Bước 7) Sau khi tạo xong ‘Login Test’ sẽ hiển thị ở dưới thư mục ‘Manual’ test với các tab khác được tạo như hiển thị phía dưới.

Bước 8) Click chọn ‘Design Steps’ tab và nhấp vào biểu tượng ‘ New Step’ hộp thoại chi tiết mở ra và được hiển thị như bên dưới

Nhập tên Step
Nhập mô tả
Nhập kết quả mong đợi
Nhấp vào ‘OK’

Bước 9) Làm lại Bước 6 và nhập tất cả các bước có liên quan để kiểm tra chức năng. Sau khi tạo tất cả các bước yêu cầu, ‘Design Steps’ tab hiển thị tất cả nội dung đã tạo như dưới đây

Bước 10) Parameters, giúp người dùng gán giá trị cho một biến, cho phép người dùng thực hiện test với các bộ dữ liệu khác nhau. Trong trường hợp này, user name và password là 2 tham số sẽ được gán với một giá trị.

Bây giờ chúng ta sẽ biết cách làm thế nào tạo một parameters

Chọn bước kiểm tra muốn thêm tham số.
Biểu tượng ‘Parameter’ sẽ được bật . Nhấp vào sẽ hiển thị như hình dưới đây

Bước 11) Parameter dialog sẽ hiển thị như dưới đây. Chọn ‘New Parameter’ button

Bước 12) Chi tiết parameter được hiển thị ở dưới

Nhập tên parameter
Gán một giá trị cho tham số
Nhấp vào ‘OK’

Bước 13) ‘parameters’ dialog hiển thị trở lại cho người dùng

Với tham số đã tạo
Giá trị
Click ‘OK’.

Bước 14) Nào bây giờ chúng ta có thể nhận thấy rằng tham số được thêm vào trong ‘Test Step’ sẽ như hiển thị bên dưới

Bước 15) Parameters đã được tạo có thể xem/sửa trong tab parameters. Hộp thoại này giúp người dùng tạo, sửa, xóa parameter

Bước 16) Tab đính kèm cho phép người dùng tải lên bất kỳ loại tệp nào, chẳng hạn như ‘xls’, ‘jpg’, v.v.

Sẽ còn các bước tiếp theo ở phần sau.

Tài liệu tham khảo: https://www.guru99.com/hp-alm-test-plan-module.html

Test Lab in HP ALM (Quality Center)

Once the test design is completed, test execution will take place with the help of Test Lab module.
One common term you will come across in HP ALM in the Test Set module of Test Lab. If your mind triggers images of some sort of collection or a set, you are correct. Test Set is infact a collection of test cases that we intend to execute.
Test cases from the Test Plan module are called into the Test Lab module.
Changes done to test cases in the Test Lab module do not affect the parent test cases in Test Plan Module. You are free to experiment. Hence the name Test Lab!

It is better to give the test set name same as that of the module name so that all the tests within the module are contained in same test set which would be easy to execute and track.
Each test set folder is assigned to a particular cycle. This enables users to group the tests together that will be executed in a particular cycle.
This module also helps user to track the progress of the cycle as the tests are executed.
The Test Lab module consists of the following functionalities and let us understands each one of those in detail.

Hard Landing Boeing 747 at Gibraltar Airport #shorts

Plan a test suite run

Prepare the test suite to run. Assign owners and environment tags to each of the tests.

The test suite run process follows these steps:

Tip: To apply the same plan to multiple test suites, in the tests grid, select the necessary test suites and click Plan Run .

To plan a test suite run:

On the Tests tab, open a test suite.
On the test suite’s Planning tab, manage the tests you want to run:
Action Steps
Add new or existing tests

Use the toolbar buttons to add new or existing tests.

Tip: You can add the same test multiple times if, for example, you want to run the same test with different environment tags.
Remove unwanted tests
Select the test’s check box and select More > Delete.
Select tests to include in the next run
Indicate which tests you want to include in the next run using the toggle in the Include in next run column. By default, all tests are set to run.

Note: The check boxes next to the test ID do not indicate whether to run the test. Selecting these check boxes applies to other features, such as exporting, deleting, and reporting.
Set the test run order
Drag the tests to set the order in which they run.

To send a test to the top or bottom of the list, right-click the test and select Rank Highest or Rank Lowest.
Add a test to a planned suite run
To add a test to a planned suite run, right-click the test and select Add to Suite Run. In the Add to Suite Run dialog box, select the suite runs to which you want to add the test, and click Add & Close.

You can also add a run which already exists. This option is available for both manual and automated tests.
In the Planning tab, click Plan Suite Run

. The Plan Suite Run dialog box lets you define the following suite’s attributes:
Field Details Release
Select a release that you want to test. After you select a release, you can select a milestone or sprint, but they have different functions:
- Milestone: When you select a milestone, it means that the run contributes to the quality status of the milestone. A unique last run is created and assigned to the milestone for coverage and tracking purposes, similar to release.
- Sprint: When you select a sprint, it means that the run is planned to be executed in the time frame of the sprint. Sprints do not have their own unique run results, so filtering Last Runs by Sprint returns only runs that were not overridden in a later sprint. To see full run status and progress reports based on sprints, use the Test run history (manual) item type instead of using Last Runs in the Dashboard widgets.
ALM Octane assigns these values to all test runs for the tests in the suite.

Tip: ALM Octane also assigns the values of user-defined fields, if the user-defined fields have the same name and type in both the test suite run entity and its test run entities. This is available if the COPY_RUN_SUITE_UDFS_TO_RUNS configuration parameter is set to true.
Program (Optional) If you are working with programs, you can select a program to associate it with the suite. All of the runs in the suite are assigned to this program, which is recorded in each run’s history. For details, see Programs. Default environment tags and Default run by
Specify the Default environment tags and Default run by to be used by all test suite runs.

The test suite run’s Environment tags and Run by fields inherit the default values. If the Default run by field is left empty, test runs are not assigned to any user. You need to manually assign each of the planned test runs to a user.

Data access: If a test belongs to a data category that falls outside of the default tester’s role, the run is not assigned to the default user. Manually assign the test run to an accredited user. For details, see Data access control.

Note: If you modify the Default environment tags and Default Run by fields after planning a test suite, the changes only affect new runs. The existing runs continue to inherit the original default values.
Enforce order for manual
When running a suite containing manual tests, set this field to Yes to enforce the run order of the tests in the suite. For details, see Enforce manual test run order.

You can change the value of this field for a suite run only when creating the suite run. After a suite run has been created, this field becomes read-only and cannot be changed.

Tip: This field might not be visible by default. To show it, click Customize Fields

and select Enforce order for manual from the dropdown.
In the Plan Suite Run box, click Plan.

ALM Octane creates or updates the suite run and test runs for the suite’s tests.
Users can run the planned tests from one of the following areas:

Area

Details

My Work module

ALM Octane displays test runs in the user’s item list in the My Work module.

ALM Octane labels each assigned run with the name of the suite run and a link to the individual test.

Select the test, and in the right pane of the My Work module, click Run

If all tests in the suite are assigned to the same user, they appear in My Work as a suite run. Select the suite run and click Run

Team Backlog or Quality modules

On the Details tab of the suite run, click Run

If you are running the entire test suite, and some tests are not assigned, indicate whether to run your assigned tests with the unassigned tests or all the tests in the test suite.

Note: When you plan a suite run, it may take some time for you to see the planned runs, since they are created in an asynchronous manner.

Optionally, you can export the test suite information in the Excel or CSV format. The export saves all fields, with the exception of UDFs (user-defined fields), and the following built-in fields: Author, Backlog coverage, BDD Spec, Builds, Component, Covered automated test, Covered manual test, Covered requirement, Data table, External test ID, Flag rules, Flags, Followed by me, In my work, Is draft, Is in latest version, Manual, Owner, Quality stories, and Test level.

How to Create Test Resources

To create test resources in HP ALM, perform these steps:

Open HP ALM and go to the “Test Plan” module and click on the “Resources” tab.
Click on the “New Test Resource” button.
In the “New Test Resource” dialog box, select the type of resource you want to create, such as “Test Script” or “Test Set.”
Enter the required information for the resource, such as a name and description.
Define the properties and fields of the resource based on your testing requirements.
Click on the “Save” button to create the resource.
After the resource is created, you can modify its properties and fields by selecting it in the “Test Plan” module and clicking on the “Properties” tab.
You can also associate the resource with other ALM entities, such as test cases or requirements, to track their usage.

Following Our Uncontainable God | Kathryn Krick

Plan tests in ALM

The following procedures summarize how to plan tests in ALM.

Higher-level task: This task is part of a higher-level task. For details, see ALM lifecycle.

Prerequisite:

A set of requirements is defined in the Requirements tree. For task details, see Requirements.

Tip: You can automatically create tests based directly on your requirements in the Requirements module. For details, see the step for converting requirements to tests in the Create requirements task.

To plan tests:

Create a test plan tree.

Create a test plan tree of test subject folders and tests. For task details, see Create tests.
(Optional) Create dependencies with test resources.

You can associate tests with a set of resources that you upload to the ALM repository. You can then view these dependencies and determine the resources that are in use. For details, see Test Resources.

Business Process Testing: You can associate component design steps with application area resources that you upload.
Define test parameters.

To make tests more flexible, you can include parameters in test steps. This enables you to run the same test repeatedly and assign different values to the parameters. For details, see Test parameters.
Define test configurations.

To run tests for different use-cases, you can define test configurations. This enables you to run the same test under different scenarios. For details, see Test configurations.
Create test steps.

Create test steps describing the operations to perform and their expected results. After you define the test steps, decide whether to perform the test manually or to automate it. For details, see Design tests.
Automate tests.

After designing test steps, decide which tests to automate. Factors influencing test automation include frequency of execution, volume of data input, length of execution time, and complexity. For details, see Design tests.
System Tests You can also create automated system tests that provide system information for a machine, capture a desktop image, or restart a machine. For details, see Create and run system tests. UFT Developer Tests You can also create or import automated UFT Developer tests. For details, see Create and import UFT Developer tests.
Create requirement coverage.

Link each test in the test plan tree with a requirement or requirements in the requirements tree. By defining requirements coverage for a test, you keep track of the relationship between the tests in your test plan and your original requirements. For details, see Create requirement coverage.
Link a test to a defect.

Link a test to specific defects. This is useful, for example, when a new test is created specifically for a known defect. By creating a link, you can determine if the test should be run based on the status of the defect. For details, see Linked Defects/Entities Page.
Analyze test plan data.

Analyze the test plan by generating reports and graphs. Use one of the following:
View dynamic graphs of test subjects In the test plan tree, select a test subject, and click the Live Analysis tab. For task details on generating live analysis graphs, see Live Analysis graphs. View test plan data in a graph On the Test Plan module menu, select Analysis > Graphs. For task details on generating graphs, see Generate an entity graph. Create a report of test plan data On the Test Plan module menu, select Analysis > Project Report. For task details on creating reports, see Create and configure project reports.
For details on additional analysis tools in ALM, see Analysis.
Establish a baseline.

After your test plan has been reviewed and approved, you can create a baseline. A baseline provides you with a snapshot of your test plan at a specific point in time. Use a baseline to mark any significant milestone in the application lifecycle. The baseline then serves as a point of reference against which changes can be compared. For task details, see How to Use Libraries and Baselines in ALM.

Test Plan Module in HP ALM (Quality Center) Tutorial

After defining requirements, development team kick starts their design and development process while Testing team start designing tests that can be executed once the build is deployed.
Success of any product depends on the testing processes and the quality of testing that is being carried out. A Good Test Plan results in a bug free product.
ALM supports maintenance and execution of manual, automation and performance tests as ALM is seamlessly integrated with all HP products such as HP UFT and HP Load Runner.

Before you plan tests

Before you plan tests in ALM, outline a strategy for achieving your requirements, as defined in the Requirements module. Ask yourself two basic questions:

How should you test your application?

What resources do you require?

Example: Consider a flight reservation application that lets you manage flight scheduling, passenger bookings, and ticket sales. Testing will require designing both manual and automated tests. You could assign testing personnel with programming experience the task of designing automated tests, while non-programmers could design manual tests.

AutoGen Studio: Build Self-Improving AI Agents With No-Code

Introduction

The test plan module in HP ALM provides a structured approach to test planning and management. It helps users to define the testing requirements, organize test cases, allocate resources, and monitor the progress of test execution.

The module enables users to generate comprehensive reports on testing activities, allowing them to analyze test results and identify areas for improvement. In this module, users can define the scope of testing, create test cases, assign them to testers, and track their progress.

Overall, the test plan module in HP ALM is a critical component of software testing activities. It helps users to manage the testing process efficiently and effectively, enabling them to deliver high-quality software that meets the needs of their customers.

Overview

The test plan module in HP ALM is a crucial part that helps users to manage test cases and scripts required to execute. A good test plan helps the user to improve the efficiency of their testing activities leading to better software quality and customer satisfaction.

Some of the benefits of using test plan modules in HP ALM are improvement in test planning, streamlined test execution, test case management enhancement, and comprehensive test reporting.

Uploading Tests

Sometimes, user won’t be creating test cases manually as it is pretty much time consuming process. Most Organizations develop manual tests in Excel and upload into ALM in bulk rather than creating each manual tests one by one. In order to facilitate uploading into ALM, HP has come up with an Addin with which the user can upload from MS excel/MS Word directly. Let us understand the step by step procedure to upload requirements into QC from Excel.

Manage suite runs

The suite run’s Runs tab lets you manage the runs by changing their rank or other attributes. Use the right-click menu to add items to My Work or to send them as an email.

Tip: To update details for multiple test runs, do a multiple selection and choose Bulk Update from the context menu.

To manage the suite runs:

Select the Suite Runs tab. ALM Octane displays a list of all suite runs.
Click on a suite run. ALM Octane opens the Runs tab and displays a list of runs.
To change the status of a run, modify the Native status in the Details tab and click Save. For example, if a run was previously blocked, you can change its status to Planned.
If you want to run a test twice as part of a suite run, make a copy of the run by selecting it and clicking Duplicate Run. If you want to redo a run from scratch, duplicate the run, make sure the copy’s status is set to Planned (this is the default), and delete the old one.
Rank and reorder the runs by dragging them to the desired location.

You cannot change the order of a run which is currently running.

Tip: To ensure that the results stay aligned with their corresponding runs, keep the runs in the same order as they appear in the suite run, and do not run tests in parallel.
If you need to change the test assignment or an environment tag, modify the values in the Run by and Environment tag columns. The assignees receive a notification in their My Work area.

Note: Environment tag is an information label. ALM Octane does not select or detect the environment on which the test runs.
After you assign all the tests, the Runs tab displays the updated list. The Smart List view is shown below:

HP ALM - Importing Requirements from Excel — HP ALM – Importing Requirements from Excel

Setup Test Plan in ALM

To set up a comprehensive test plan in HP ALM, we need to consider some points to ensure complete test coverage and effective testing.

Start by creating a new test plan in the Test Plan module of ALM.
Define the scope of the testing by identifying the specific features, functionalities, and components that need to be tested.
Set the testing objectives and create individual test cases within the test plan module.
Defining and organizing the test cases based on the testing objectives and functionalities.
Assign roles and responsibilities to team members for executing the tests, recording results, and reporting defects.
Setting the test timelines and ensuring complete test coverage.
Log any defects discovered during testing and manage the resolution process.
Update the test plan based on the testing results and feedback.

How to Create a Test Set

Step 1) First step is to create a root folder as a container for having the test sets. We can name it in line with the release and cycle so that it is easy to track.

Goto ‘Test Lab’ Module under ‘Testing’ Tab
Create a new Folder by Clicking on ‘New Folder’ icon.
The ‘New Test Set Folder’ Dialog opens. Enter the name of the folder as ‘2017 R1 – Cycle 1’.
Click ‘Ok’

Step 2) The Test Run Folder would be created as shown below.

Step 3) Select the created folder and assign ‘Cycle’ to it which means the entire test set should be executed for Cycle 1.

Step 4) Enter the name of test set and click ‘OK’

Note: The Target Cycle field is disabled as the target cycle is selected at the folder level(2017 R1 – Cycle 1).

Step 5) After creating the test set, we need to select the tests and add it to the test set.

Select the Test Set.
Navigate to ‘Execution Grid’.
Click ‘Select Tests’ Button. The Test Plan Tree opens up.
Select the Tests to be executed for this Cycle.
Click ‘<=’ button. This will move/pull test cases from test plan to test lab.

Step 6) Upon adding tests from test plan tree, all the configuration parameters of the selected tests are displayed to the user. User can edit the configuration before adding it to the test lab.

Note: User has no control over test configuration selection in test Lab. Hence the entire configuration will be added to the test set by default. In case one of the selected configuration is NOT part of the cycle, after adding the tests, delete from the test lab.

Step 7) After selecting the configurations, the selected tests are added to the test set. In this case we have selected all three configurations; hence we can find three instances of ’01- Login Test’.

Step 8) Repeat the above steps to create more test sets and select all the relevant tests planned for this cycle. After creating all test set, the structure of test set will be as shown below:

Step 9) The other important tab that we need to understand is ‘Execution Flow’. Select ‘Execution Flow Tab’ which displays the order in which the tests would display during the execution. Users can also change the execution order using this tab which will be dealt in a separate section of this module.

Software testing using excel - How to build test cases — Software testing using excel – How to build test cases

How to create Test Run Schedule

Testers can control the test execution with the help of “Execution Flow” Tab. Testers can also specify date and time for executing a particular test instance. We can also schedule the test based on the results of another specified test instance in the Execution Flow.

Now, let us understand how to schedule the test flow in HP-ALM.

Step 1) Select “Execution Flow” tab from Test Lab module.

Step 2) Double click on the specific test against which the schedule needs to be set. “Test Run Schedule” would be displayed as shown below. We can notice that there are no execution conditions that were set by default.

Step 3) To Add an execution condition, click on “+” icon as shown below.

Step 4) The New execution condition dialog opens up.

Select the test from test drop down. All the tests in the test set will be displayed
Select the condition. It can take either ‘Passed’ or ‘Finished’.
Click ‘OK’.

Step 5) The test run schedule is displayed with the added execution conditions.

Step 6) The Execution flow realigns automatically as show below. According to the below displayed flow, the test ‘Cluster Head’ will be executed only when the ’02 – Reset Button Check’ is finished.

Step 7) Nowlet us understand how testers can specify the date and time in execution flow for executing a particular test. It is more helpful when testers know about the readiness of a specific functionality or for scheduling automated tests.

Let us say, the manager login profile would be ready only after a specific date. Hence testers can execute the same by specifying the conditions in ‘Execution Flow’.

Double Click on the test for which the execution flow criteria needs to be set.

Step 8) Now,

Navigate to ‘Time Dependancy’ Module
Select ‘Run at Specified Time’
Enter the Date on which you would like to execute
Enter the Time when you would like to execute the test
Click ‘Ok’.

Step 9) Theexecution flow tab will be realigned as shown below. This kind of scheduling is very much helpful for automated tests which follow the same steps.

Note: Ifthe scheduled date and time has arrived, then ALM would automatically launch the tests. It holds good for automated test as test would be executed without any manual intervention. The Precondition for triggering the tests automatically is that the host should be ready(shouldn’t be powered off or locked) and it should be in a state to trigger the test. If it is a manual test then there won’t be any effect.