Integrating Selenium with Confluence and JIRA

Open Source Test Management within Confluence, Automation of Selenium, Reporting, and Traceability

Andrew Lampitt, Co-Founder Sanjiva Nath, CEO and Founder

•  zAgile  corporate  overview  •  Challenges  with  Test  Management/Automa9on  Today  •  Wikidsmart  pla>orm  and  product  overview  •  Wikidsmart  QA  overview  and  demo  

–  Achieving  test  case  management  within  Confluence  –  Automa9ng  test  case  execu9on  using  Selenium  –  Tracking  and  Repor9ng  on  test  results  

•  Q&A  

Agenda  

2  

•  Mission: Integrate Teams, Tools, Processes, and Knowledge –  Primarily targeting Application Lifecycle Management / Software Engineering –  Platform extensible to any domain and applications

•  Founded: 2006 in San Francisco, launched v1.0 in 2009

zAgile  Corporate  Overview  

•  Press Coverage

•  Selected Customers

•  Partners

Technology Services

3  

Combining the Strengths of Confluence and JIRA

•  Confluence  – Ease  of  Content  Crea9on  – Ease  of  Collabora9on  – Accessibility  

•  JIRA  – Task  Management  – Extensible  Workflow    

 4  

Challenges with Confluence-JIRA Integration

•  Seman9cs  of  a  page  not  defined  –  Does  it  represent  a  Test  Suite,  Test  Case,  or  Feature  ?  

•  Establishing  formal  links  to  other  objects  (author,  reviewer,  project,  stakeholder)  

•  Embedding  JIRA  Task  info  in  a  page    –  Formal  rela9onship  not  captured  –  Rela9onship  not  accessible  anywhere  (including  JIRA)  –  Nature  of  rela9onship  implied  (i.e.  is  it  an  approval  task,  a  development  task,  a  test  task)  

–  Inability  to  access  other  task-­‐related  informa9on  (ex:  result  of  task  execu9on  performed  using  Selenium)    

•  Cannot  link  page  to  execute-­‐ready  Selenium  scripts  •  Limited  informa9on  sharing  between  Confluence  and  JIRA  

 

5  

Challenges with JIRA Test Management

•  Defini9on  of  Test  resides  with  Execu9on  (in  same  task)  – Clone  for  each  execu9on  – Can’t  easily  capture  execu9on  results  related  to  a  Requirement  or  Feature  

•  Test  execu9on  results  cannot  be  easily  9ed  to  Confluence  ar9facts  – Which  requirement  has  what  test  cases  and  when  were  they  executed  with  what  results?  

•  Integra9on  with  Selenium  for  automa9on  

 

6  

Challenges with Test Automation

•  Lack  of  a  structured  repository  for  managing  Selenium  scripts  

•  Inability  to  associate  a  script  with  a  test  suite,  test  run  or  test  case  

•  No  way  to  map  results  of  script  execu9on  with  test  defini9ons,  features  

•  Can’t  9e  script  execu9on  to  workflows  •  No  repor9ng/analy9cs  associated  with  test  execu9on  across  itera9ons,  releases,  requirements,  etc.  

7  

•  Wikidsmart  “unites”  your  environment:  •  Cohesion  of  content  amongst  tools  &  applica9ons  

•  Traceability  •  Interoperability    •  Easily  find  content  with  federated  search  of  concepts  

•  Automa9on  •  Content  flow  amongst  applica9ons  and  tools  •  New  content  crea9on  amongst  apps  and  tools    (e.g.,  wiki  page  from  a  new  account,  new  task  from  a  closed  opportunity,  etc.)  

•  Consistency,  easy  maintenance  of  content  

•  Turns  JIRA  and  Confluence  into  an  applica9on  pla>orm  •  New  applica9ons:  same  GUIs,  leverage  JIRA  workflow  

Wikidsmart  Pla8orm  Benefits  

8  

Wikidsmart  Architecture  Overview  (1  of  2)  

9  

Wikidsmart  Architecture  Overview  (2  of  2)  

10  

•  Wikidsmart  PM  –  Requirements  management  within  Confluence,  9ed  to  JIRA,  Greenhopper  and  other  tools  for  traceability  

•  Wikidsmart  QA  –  Test  Case  management  within  Confluence,    integrated  with  JIRA  and  Selenium  for  workflow-­‐based  automa9on  and  traceability  

•  Wikidsmart  ALM  –  PM  and  QA,  plus  integra9on  with  Jenkins  and  FishEye  (version  control:  Subversion,  Git,  CVS,  Perforce,  and  Mercurial)  

•  Wikidsmart  CRM  –  JIRA  and  Confluence  integra9on  with  Salesforce.com  for  Customer  On-­‐Boarding,  Customer  Case  Management,  etc.  

Wikidsmart  ApplicaCons  

11  

•  Easy  install  “unites”  Selenium  with  JIRA,  Confluence,  etc.  •  RESTful  integra9on  •  Achieve  all  func9ons  as  if  one  system    

–  Bi-­‐direc9onal  linking  and  synching  of  Selenium  concepts  with  JIRA  issues  and  Confluence  pages  

–  Confluence:  •  Create  structured  wiki  page  for  test  management  •  View  Selenium  test  results  and  reports  within  Confluence  

–  JIRA  •  Associate  one  or  more  JIRA  Issues  to  a  Selenium  test    •  Associate  mul9ple  Selenium  tests  to  a  JIRA  Issue  

–  Report  across  JIRA,  Selenium  and  more.  Display  reports  in  Confluence,  portal,  or  elsewhere  

Wikidsmart  QA  Features  

12  

•  Manage  Test  Cases  in  Confluence    •  Automate  using  Selenium  Test  Scripts  •  Create  Test  Runs  for  Itera9ons  •  Execute  Test  Scripts  through  JIRA  Workflow  •  Automa9cally  Capture  Test  Execu9on  Results  •  View  Test  Results  in  Dashboards  for  Features,  Requirements,  Components,  Releases  &  Projects  

Achieving Full Cycle Test Management

13  

•  Wikidsmart  contextually  integrates  content  from  any  sokware  engineering  tool  

•  Guarantee  traceability,  interoperability,  and  federated  search  of  all  content  across  your  environment  

•  Manage  tests  within  Confluence  •  Automate  Selenium  tes<ng  and  more  with  deep  interoperability  with  JIRA,  Confluence  and  others  

Summary    

14