Test Automation management and team collaboration

http://gredy.net@ImGredy

A tool which answers a question «How to make test automation contribution visible and profitable?»

Test automation management tools

… are specific tools providing test automation collaborative environment that is intended to make test automation efficient, clear for stakeholders and traceable. Since test automation is becoming cross-discipline (i.e. mixes both testing and development practices), the need of specific and dedicated environment for test automation is becoming vital.

There are…

Too complicated and overdesigned tools and dashboards

And there are…

too primitive ones

Motivation

Test automation usually lacks of reporting, analysis and providing meaningful information about project status from automation perspective. Eventually it is lack of value…

Classical Test management systems from the other hand mostly targeted on manual effort and cannot give all tangible information and capabilities

How special tool will help?By:

o Making transparent, meaningful and traceable reporting for all project stakeholders

o Easing test debugging through built-in test results analysis workflowo Providing valuable metrics and KPIs – both technical and business-wise

(trend analysis, benchmarking, gap analysis, root cause analysis, risk point analysis)

o Grid benchmarking and comparison of test execution days reduces analysis and review effort

o Clean traceability with other testing artifacts (test cases, data, issues, etc)o Keeping historical data in a single place, easily retrievableo Post project analysis and automation performance assessment (basically

progress of test coverage shows the group performance)

Our Clients: Case Studies at glanceE-commerce Company:"We rely significantly on test-automation to reduce time to market our products. Gredy made our automated testing process well established and efficient."

Global Finance Company:"Our overall software lifecycle have been benefiting from use of Gredy and as more test automation we have as more we realize necessity to have test automaton management tool"

Navteq, GIS:"We were able to deploy and integrate Gredy with Soap UI within one day. Since then we deliver nice daily reports to managers. Also the tool gets rid of tedious daily results by showing comparisons against previous days"

Security Company:"Test automation is an integral part of our continuous integration. Results are huge and unstable from day to day. We are attached to Gredy, it is a must to have tool for us from this point"

Continuous test execution

SCM

Prod (Stable) TestsStatic code

analysis

Prod (Stable) Framework

Depl

oy o

n Q

A en

v

Test artifacts

Test cloud

+ CommitsTriggers update

Test Reporting DefectsBenchmark analysis Metrics

Test code changes

Test Reporting

DB

fills

facilitating

promotes

Traceability

Test automation ecosystem with Gredy

Continuous Integration

On demand, scheduled

Easily Integratable with any ITE or infrahttp://gredy.net/UserDocs/Gredy%20Specs%20-%20Data%20submission.pdf

Dashboards

Collaborative environment for automation engineers

KPIs and analytics

Wiki style Updates

Built-in issue tracker

http://gredy.net

Test Runner – Queue Job

Stand(s) DNS/IP (if multiple - separate by comma or space)

Date:

Time:

Max Duration:

Interrupt on new Job?

Repeat Job N times:

Kill the current Job?

Job Priority:

Kill the current job if its priority is less than:

Queue the Selected

Further Steps?

Further Steps?

More:

Test queue and schedulingTest Runner API for CI or whatever to trigger runBackward integration with CI toolsPlug-ins and ALM integrationChange history and audit trails…We will keep it lightweight and simple

Your ideas too - http://code.google.com/p/gredy/issues/list

Learn more at http://gredy.net/Gredyhowto/Gredyhowto.htmland http://gredy.net/userdocs.html

Try Live Demo at http://gredy.net/Gredy/index.php

To get your FREE Gredy Team edition, send us your inquiry via http://gredy.net/contact.html (subject for discussion)

@ImGredy

A tool which answers a question «How to make test automation contribution visible and profitable?»