Mobirise Web Site Builder

AGILE TESTING

Risk based Application Lifecycle Management. ProcedureCapture® covers User Stories, Risk, Structured and Unstructured Testing, Traceability and Defects.
All from one integrated, affordable and easy to use tool.

ProcedureCapture®

Risk Based Agile Application Lifecycle Management

USER STORIES

Seamlessly manage your User Stories, Sprints, Acceptance Criteria and Product Backlog including their own hierarchy and versions.
Real time view of their traceability against Test Scripts and Defects allowing a clear understanding on what is "Done".

RISK

Systems and User Story Risk Assessment.
Focus your testing scope and rigor on what is important. 
Different models allow flexibility in terms of Risk Priority and also Risk Detectability. Allows users to select which risk model they want to use by system.

AGILE TESTING

Ability to create both Structured and Session Based testing. Create Automated UI and Manual UI Tests within the tool. 
Takes inputs from Unit and Component tests and works with ATDD and BDD methodolgies  to give you an overview  and confirmation of your Acceptance Criteria and Definition of Done.

DEFECTS

Risk Based Priority Defect Management - traces the Defect risk priority back though the Tests and back to the User Story.
Defect tracking ?allows the complete tracking of a Defect throughout its lifecycle.

STAKEHOLDER COMMUNICATION

Demonstrate and validate Sprint deliverables to internal or external stakeholders. Easily created Video of completed functionality and testing reports.
Both of which are usually small enought to be e-mailed. 

USER STORIES

ProcedureCapture allows you to :

  • Create User Stories and their Acceptance Criteria.
  • Manage Sprints, product backlogs and  see how sts and back to the Requirements.  
  • Editable User Story and Acceptance criteria grids with the ability to filter, group and sort.
  • Define the linkage and hierarchy between User Stories and thier Acceptance Criteria.
  • Workflow control of User Stories and and ability to require Electronic Signature for approval if required.
  • See real time traceability of your User Stories to Test Scripts throughout the project lifecycle.
  • Version control and complete history of each User Story change.
  • Output your User Story reports (including versions) throughout whole lifecycle.

RISK ASSESSMENT

  • Both System and User Story Risk Assessment.
  • Different risk assessment models ?allows flexibility in terms of Risk priority levels and also Risk Detectability. Allows users to select which risk model they want to use by system.
  • Versioning the risk assessment, so that you can have a ‘before?and ‘after?risk assessment, showing what the risks are before mitigation/testing and after mitigation/testing.

From this Risk assessment, you can then ensure that the testing includes the necessary level of scope and correct degree of test rigor thus reflecting the risk level. This enables the level of testing detail to be appropriately scaled to the risk.

AGILE TESTING

AGILE TESTING

Agile Testing differs from the "Big-Bang" test at the end approach of traditional development. Rather than this, code is developed and tested in small increments often with the development of the test preceding the development of the code.

As the above quadrants show, there are multiple different kinds of testing the agile team can perform to increase the quality and reduce the number of bugs and issues.

ProcedureCapture can perform the testing required in Q2 and Q3 and can take inputs from tools for the results in Q1 and Q4.
It provides this all in a risk based manner  while also given real time traceability between User stories, Acceptance Criteria, Tests and  Defects found. 

SESSION BASED TESTING

Session Based Testing (SBT) can be a more dynamic and powerful approach which discovers critical problems in an extremely efficient way.
It works well for continuously changing tests based on everything learned so far and does not suffer from the scripted approach where you may miss the same things every time.
To record a Session simply define the Test, its Charter and the time to run for and your session will then be recorded as a "Visual Storyboard". 
This has a recording of all the steps that have been completed during the session and any issues, defects or errors found. This can then be saved as a video which is usually small enough to then be emailed and provides the explanation of your exploration and the context of what you have been doing.
The SBT session asset can then be distilled down to the relevant steps to form your structured tests .

STRUCTURED UI TESTING

Using a mix of both Session Based and Structured testing is gaining recognition as being one of the most efficient approaches to System Level Acceptance tests and Usability testing.

ProcedureCapture works on all applications , does not need script programmers and allows you to use the same captured asset for both Session Based and Structured UI testing.

Once you have recorded an Exploratory session, you can distil down and save relevant visual steps into structured UI test cases which then can be re-run in both an Automated or Manual mode. 

DEFECTS

Risk Based Priority Defect Management - traces the Defect risk priority back though the Tests and back to the User Story.  

Defect tracking ?allows the complete tracking of a Defect throughout its lifecycle.

  • Risk Based Priority Defect Management - traces the Defect risk priority back though the Tests and back to the User Story which means you fix the most important defects first. 
  • Defect tracking ?allows the complete tracking of a Defect throughout its lifecycle and gives the whole team transparency of its status. 
  • Role-based Defects work flow - specific role is required for each Defect transition allowing the control and management of the process.    

STAKEHOLDER COMMUNICATION

Effective communication is a fundamental requirement for agile modeling. 

This communication is both internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams)

ProcedureCapture can be used to do the following:

  • Share Sprint functionality as a "visual storyboard" and easily create a shareable video - usually small enough to be e-mailed. 
  • Show UAT and UI tests and their results - either Session Based Tests or Scripted tests. 
  • Show the traceability between User Stories, their Acceptance criteria and the test results for each to reach agreement on "done" for a Sprint.    

 

CONTACTS
Email: US@raltus.com
Email: Europe@raltus.com
Email: Ireland@raltus.com

Air Max Classic pas cher
Canada Goose parka Jasse
Billiga UGG classic mini Outlet
Canada goose outlet
NIKE Air Max 95
Cheap Air Max 1
Canada Goose jackor herr
Michael Kors h ndvesker
Canada Goosejakke
Cheap Air Max fille