How to login HP ALM tool

How to start ALM:
Step #1: To start ALM type the address http://[<:port number="">8080]/qcbin
Step #2: Click “Application LifeCycle Management” in the below window.


                 

Step #3: Enter the user name and password. “Authenticate “button gets activated. Click on it. The Domain and Project fields get activated. Depending on your login credentials you have access to certain projects. (This information is set by your ALM Admin).

         


Step #4: Choose the Domain and Project as required and click “Login”. Once you are logged in, ALM window opens up and displays the module in which you were working last.

1.Domain is nothing but a logical division of departments for your organization. Example: Banking, Retail, Health Care etc.
2.Projects are the different teams working within the domain. For example in a Retail project, they could be working on the front end store Point of sale app or the back end inventory module.
The Domain and Project information is set by the ALM Admin.

                  

HP Application Lifecycle Management Introduction

1.Introduction to HP Application Lifecycle Management/Quality Center:
 
HP ALM formerly known as Quality Center is a Test Management tool to manage entire Quality Assurance and testing process for an organization. Before being called HP Quality center it used to be called as Mercury Test Director.
 
In my experience I have come across many projects (Manual , Automation and Performance) that is used for all areas of testing, it is a testing suite and is a very simple tool to use, extremely user friendly. Even if you have never used it before, chances are you will be able to figure out how to in a really short time. However, there is a lot of difference between being able to navigate through the tool and being able to exploit its potential to benefit your project.

If you have a compatible machine and understand the components ALM has.
Briefly, the following are the components:

•    A server
•    A client
•    Database

Each component has a certain version that is compatible with ALM.

Why is ALM/QC used?

ALM helps make project management, from requirements to deployment easier. It increases predictability and creates a framework to manage projects from a central repository.  With ALM you will be able to:

Define and maintain requirements and tests
Create Tests
Organize tests into logical subsets
Schedule tests and execute them
Collect results and analyze the data
Create, monitor and analyze defects
Share defects across projects
Track progress of a project
Collect metrics
Share asset libraries across projects
Integrate ALM with HP testing tools other third party tools for a complete automation experience.

Jira Agile issue types

JIRA Issue Types

There are generally 5 Jira issue types the 5th one is Sub-task,  can only created from within a Story.

    Epic

• An Epic is used when a feature is large in scale, may take several sprints to complete, and/or may spans multiple components.
• The Epic itself is an umbrella issue. An Epic is comprised of one or more stories.
• Usage: Anyone can create an Epic and put it in the backlog for a project.

    Story

•  A Story or user story is a piece of work that can be completed within a sprint.  It is usually part of an Epic.
• Usage: Anyone can create a Story and put it the backlog for a project.

    Bug

• A Bug is a defect, an error, or a flaw that requires a fix, it can be a code change, a documentation update, configuration change, etc…
• Usage: Anyone can create a bug and assign to himself or someone else or leave it unassigned if they wish someone else to pick it up and work on it

    Task

• Task can be used to breakdown a story into smaller work units that can be completed in a day or two; however, for deconstruction of a story, it is recommended that a Sub-task be used. Using a Sub-task will save the user Jira steps and will be automatically linked to the story since it's created from within the story.

 See Sub-task below.

Tasks can be used to track discrete activities that must be done and may not necessarily be related to a story (for example, fix a Jenkins job); however, if a user chooses to use Task issue type to track work associated with a story, be sure to link the Task to the Story via the Linked Issues and Issue fields as illustrated below.
     
Usage: Anyone can create a task and assign to himself or someone else

 Sub-task

• Sub-task is used to breakdown a story into smaller work units that can be completed in a day or two. Breaking a story down into discrete work units that can be burned down daily will communicate progress on the story.
• Sub-tasks are created from within the story via the More menu option by selecting Create sub-task

Managing shared filters and dashboards

JIRA allows end users to create their own search filters and dashboards and share them with other users. When the owner of the shared filters and dashboards leaves the organization or goes on leave, others will not be able to make changes to them. In these cases, as the JIRA administrator, you can temporarily (or permanently) change the owner of the shared filter and dashboard to a new user.

Steps to follow :

Perform the following steps to reassign a shared filter or dashboard to another user:

•  Navigate to Administration | System | Shared filters (or dashboards).
• Search for the shared filter.
• Select the Change Owner option for the filter.
• Enter a new owner for the filter, for example, yourself, and click on the Change Owner button.

JIRA Agile Software workflow

The simplified workflow and setup in this tutorial is intended for teams using scrum, so some of the concepts presented may not apply to all teams. Here's how the manager and users work together to complete a sprint:

Roles

Typically, variations on the following roles can be found in an agile development environment. We recommend that managers complete both tutorials while users complete the user tutorial.

JIRA Software Managers
User with administrative rights for your instance of JIRA Software. These roles are usually filled by scrum masters or development managers.

JIRA Software Users

User who works on and resolves issues. These roles are normally filled by software developers.

Selenum now supporting to test windows based applications with the help of winappDriver

WinAppDriver: WinAppDriver (short for Windows Application Driver) is a free test automation tool for Windows desktop apps developed by Microsoft. It can run as a standalone as well as a plugin for Appium. Thus, if you are already running Appium’s server, then a request for Win10 app automation will launch WinAppDriver.exe.

Pros:

It’s developed by Microsoft (which in itself is awesome!), and it makes perfect sense to test Windows desktop apps using a tool from the same company.

It uses WebDriver protocol which means that if you’re from the web/mobile automation world and you already know how to develop using the WebDriver environment, then the transition to WinAppDriver will be easy, quick and clear for you.

Cons:

WinAppDriver is a free tool, yet currently its code is not open source. Samples, tests and related tools are open source, and it’s mentioned that they are considering the option to open source the WinAppDrive code.

Bottom Line:  A fast-growing tool that will that will provide you with better support for using Appium to test Windows apps.