1. HPE ALM Octane

2. Content Introduction Demo Questions Background for ALM Octane
Key features today
Upcoming features
Feature highlight: DevOps
Feature highlight: BDD and Gherkin
Requirements
Demo
UI Tour
Presenting UI and walking through modules
Testing in Octane
Manual test
Test suite
Gherkin test
Making a defect
Questions

3. ’QC’ Test Director -> Quality Center -> ALM
At June 2016, with version 12.53, QC / ALM is
HPE ALM.Net with several editions: HP ALM, HP Quality Center (QC) Enterprise Edition, HP ALM Performance Center Edition, HP Quality Center (QC) Express Edition, HP Quality Center (QC) Community Edition
At the same time, entirely new ALM is launched as parallel product
HPE ALM Octane
Current Product version:
Build time: Nov 23, :54:25 PM

4. Background
Agile has become mainstream in many big enterprises, traditional HP ALM customers
HP wants their share also in agile world
SAFe ’Scaled agile framework’ enables agile for large programs in major companies
DevOps and CI makes development faster -> real benefit for customer
ALM.Net has some historical burden, e.g. complex database, making transforming it for new challenges difficult
Still great for waterfall
Studies were done and entirely new ALM Octane was launched for agile, June 2016
Start with limited set of features, maturing during 2017

5. Key features today DevOps / CI / CD / Scrum / Kanban / SAFe 4.0*
Gherkin and BDD (Behaviour Driven Development)
Build-in Support for CI servers (Jenkins or Teamcity) and source code management (GIT of SVN)
Backlog and Task management
Test and defect management
Real time reports and meters
Tags
ChatOps / Slack
* Portfolio support on pipeline, 4 / 2017

6. Upcoming Features Requirements & Agile (Spring 2017)
Traditional Requirements
Enterprise Agile; Portfolio support (=SAFe 4.0)
Project and Portfolio Management (PPM) integration
UFT Test Management
Next Gen Synchronizer
Lightweight Directory Access Protocol (LDAP) integration

7. Feature highlight: DevOps
Agile and DevOps are similar, but while agile software development represents a change in thinking and practice that should lead to organizational change, DevOps places more emphasis on implementing change to achieve its goals.
Continuous delivery and DevOps are similar in their meanings and are often conflated, but they are two different concepts. DevOps has a broader scope, and centers around the organizational change, specifically the collaboration of the various teams involved in software delivery (developers, operations, quality assurance, management, etc.), as well as automating the processes in software delivery.
With CI server integration, Octane can display and run* pipelines and report results real-time.
*initiate run on CI server

8. Feature highlight: BDD
Behavior Driven Development focus on preventing defects rather than finding them, by writing concrete examples as acceptance criteria together as team (business-dev-test).

9. BDD In Order to [benefit] As a [role] I Want to [feature]
Narrative
In Order to [benefit]
As a [role]
I Want to [feature]
Scenario: [description]
Given [context or precondition]
When [event or action]
Then [outcome validation]
One or more scenarios
BDD (Behavior Driven Development) is similar to TDD (Test Driven Development) and ATDD (Acceptance Test Driven Development). BDD emphasizes describing behavior; what feature should so. Tests are written firsts and then code is written so that tests are passed. Tests are largely automated.
Octane supports Gherkin in writing tests for BDD. Automation is done with Cucumber within IDE like Visual Studio. Cucumber works with all the major software platforms including Java, .NET (SpecFlow), JavaScript, PHP (Behat), Python (Behave) and Ruby.
Automated tests are located in Source Code Management server.
There is a process for updating tests later, making Gherkin tests a living document.

10. Gherkin Feature: Updating cucumber stock value Background:
Given Cucumbers are available and tester is hungry
Scenario Outline: Eating
Given there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
Examples:
| start | eat | left |
| | 5 | 7 |
| | 5 | 15 |
Scenario Outline: Eating
Given there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
Examples:
| start | eat | left |
| | 5 | 7 |
| | 5 | 15 |
Scenario: Given When Then
Scenario: Eat 5 out of 12
Given there are 12 cucumbers
When I eat 5 cucumbers
Then I should have 7 cucumbers

11. BDD flow with Gherkin
BDD tests are ‘the single source of truth’, and also a living document through application life-cycle.

12. Requirements System requirements to fully utilize features of Octane:
Integration to CI server (Jenkins or TeamCity)
Integration to SCM server (Git or SVN)
Compatible development environment (for IDE plugin and Cucumber)
SaaS and on premise installations
Browsers:
Chrome 45 and higher
Firefox 38 and higher
Internet Explorer 11
Apple Safari and higher
DevOps pipeline setup within CI server, may include various tools
Cucumber setup within IDE, different variations depending on developing target

13. UI Tour

14. Testing

15. Testing Test Plan and Test Lab are gone!
Instead: Application area with 3-level structure
Test is associated with application functionality for finding it in organized 3-level tree.
During sprint test is associated with Feature
Test suites to include multiple tests, similar to test set in QC Lab
Also Features and Defects can be found in application area
Manual tests have Setup steps, Validation steps, and Call steps
Test steps are text format -> easy to copy paste content
Test steps have no columns, step is a line without columns
Tests include also test run information (no more Test Lab)
Support Gherkin language for automating tests
Displays both manual and automated runs within Gherkin test
Continuous integration
Tracking health of build, release and application

16. Manual test 3 kind of steps available: Setup step: “- “
Add a setup step when the tester has to perform an action, without indicating if the action passed or failed.
Validation step: “- ? “
Add a validation step when you want the tester to be able to specify a pass or fail status when running the test.
Call step ” (1234=id of called test)
Add a call step to have the current manual test call another manual test.

17. Test suite
Test suites are tests that call other manual or gherkin tests. Test suites are helpful for facilitating test reuse.
When a test suite runs, each of its tests runs sequentially.

18. Thank You Questions? One month free trial: