Comment améliorer les tests de flux transverses à vos applications métiers ?
•Download as PPTX, PDF•
0 likes•365 views
Les entreprises doivent faire face à des changements en continu pour suivre le rythme de plus en plus rapide de leurs activités. Dans ce webinar, vous pourrez écouter les meilleures pratiques et les conseils pour le testing des processus métier qui vous permettra de réduire vos cycles de tests de 30%. Venez écouter notre expert technique, Serge Lazami de Panaya, qui vous fera part des bonnes pratiques en terme de management et d’accélération des tests de vos flux transverses multi-applications.
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (16)
Similar to Comment améliorer les tests de flux transverses à vos applications métiers ?
Similar to Comment améliorer les tests de flux transverses à vos applications métiers ? (20)
More from Panaya
More from Panaya (12)
Recently uploaded
Recently uploaded (20)
Comment améliorer les tests de flux transverses à vos applications métiers ?
- 1. PANAYA© Panaya | An Infosys Company1 Panaya Test Center Comment améliorer les tests de flux transverses à vos applications métiers ?
- 2. PANAYA© Panaya | An Infosys Company2 Today’s Speakers Serge Lazimi Product Manager, Testing Solutions at Panaya Anat Grynberg Marketing Manager France at Panaya
- 3. PANAYA© Panaya | An Infosys Company Digital transformation accelerates the need of Business and IT to continually deliver business driven changes without compromising quality. 3 PANAYA
- 4. PANAYA© Panaya | An Infosys Company4 IT Spend on Testing Continual Growth of IT budget for QA and Testing Expected to rise to 40% of total IT spend, covering all aspects of QA and Testing, including processes, tools and resource costs. World Quality Report 2015-16
- 5. PANAYA© Panaya | An Infosys Company5
- 6. PANAYA© Panaya | An Infosys Company6 PANAYA Although organizations strive to relieve the testing bottleneck with automation, reality proves different.
- 7. PANAYA© Panaya | An Infosys Company7 Testing needs to mirror the way today’s global organizations run their business processes in real time, with diverse users spread through many geographies. Paradigm Shift in Testing PANAYA
- 8. PANAYA© Panaya | An Infosys Company A New Approach to Testing PANAYA End-to-End Test Management Business Process- Centric Collaboration Visibility & Optimization Quality & Compliance
- 9. PANAYA© Panaya | An Infosys Company9 What is Cross-Functional Business Process Testing PANAYA Segregation of duty (Roles and Authorizations) & Business Knowhow
- 10. PANAYA© Panaya | An Infosys Company PANAYA POLL 1/ 3 PANAYA
- 11. PANAYA© Panaya | An Infosys Company11 PANAYA For enterprise organizations that want to introduce business innovation faster but struggle to deliver continuous change, Panaya Test Center provides an end-to-end test management platform designed for business process validation, reducing test cycles by 30%, while ensuring risk free go-live.
- 12. PANAYA© Panaya | An Infosys Company12 ERP Business Process Testing Challenges Traditional tools and methodologies are not suited for functional analysts and business users Designed for generic software testing and not ERP Complicated UI designed for technical users Excel as a workaround is not scalable Lack of end-to-end business process visibility Workaround solutions are not built to support business process testing by multiple users As a result, test managers lack intuitive reporting and dash boarding Inability to track testing quality and accuracy Documentation of actual tests performed is time consuming Limited ability to capture business process knowledge Hard to free up business users time to document their daily activities Idle time between sequential testing activities Lack of collaboration tools As a result, testers don’t know when to test their part of the process
- 13. PANAYA© Panaya | An Infosys Company13 Introducing Panaya Test Center Available 6 months Roadmap Test Management Test Evidence (Capture) Defect Management Test Execution (Acceleration) Reports & Dashboards E-signature for Compliance Test Box Web Player Release Dynamix Requirements Traceability
- 14. PANAYA© Panaya | An Infosys Company14 200 global enterprises trust Panaya for testing “Panaya helped unify all of the processes and test cases in a single, reusable repository. It’s not in an Excel file, it’s in Panaya and everyone can access these particular processes.” “Panaya helped us save 30% of our testing effort while improving the quality of our testing.” “Before Panaya, we were not only doing more testing, but also potentially the wrong testing.” “We estimate a 30% savings in total testing time thanks to Panaya Test Center.“
- 15. PANAYA© Panaya | An Infosys Company PANAYA POLL 2/ 3 PANAYA
- 16. PANAYA© Panaya | An Infosys Company PANAYAPANAYA Eliminate the Business Bottleneck by Boosting your UAT’s
- 17. PANAYA© Panaya | An Infosys Company17 UAT - Typical Process in Business Applications
- 18. PANAYA© Panaya | An Infosys Company18 UAT - Typical Test Scenario Context Scenario: Requisition to Production order Country: EuropeGermany Storage location: 0001
- 19. PANAYA© Panaya | An Infosys Company19 UAT - Typical Management Platform PANAYA
- 20. PANAYA© Panaya | An Infosys Company20 UAT - Common Challenges PANAYA Poor visibility & control over testing Idle time between testers Bureaucracy / Overhead on testers Time & Cost of flying testers to the same location Lack of time of the business users for testing
- 21. PANAYA© Panaya | An Infosys Company21 PANAYA
- 22. PANAYA© Panaya | An Infosys Company PANAYA POLL 3/ 3 PANAYA
- 23. PANAYA© Panaya | An Infosys Company23 E2E solution for ERP Testing 100% SaaS, no hardware, no software installation Intuitive dashboard brings increased control and visibility Automatic handover between testers reduces idle time Automatic test run evidence reduces testers effort and brings visibility to previous steps Smart defect management increases productivity and reduces bottlenecks Automatic defect reporting allows developers to immediately start working on the solution Effortless documentation offers reusable, detailed test scripts Automatic migration of your existing test scenarios means easy on-boarding
- 24. PANAYA© Panaya | An Infosys Company24 A retenir L’automatisation des tests ne représente qu’un aspect d’une stratégie de test Les méthodologies de test intégrés doivent être améliorées Ils reflètent les flux métiers transverses qui deviennent de plus en plus critiques Les outils traditionnels de test n’adressent pas cette problematique
- 25. PANAYA© Panaya | An Infosys Company25 PANAYA Established 2006, Acquired by Infosys - 2014 Quality Automation SaaS Solution for ERP Powered by: ERP Domain expertise Crowd based customer insights Proven with over 2000+ Customers Over 200 Testing customers Over 9,000 projects (5,000 business process implementations) 2000+ Stay-current projects (upgrade, patches) Over 5,000,000 test scripts
- 26. PANAYA© Panaya | An Infosys Company26
Editor's Notes
- Organizations are aiming to deliver business driven changes fast – looking to their IT to enable change without compromising business process quality and assurance within an increasingly complex enterprise applications environment.
- Organizations are continually spending more and more to ensure that change will not compromise the business. In fact, more than a third of IT spend is dedicated to testing and quality assurance, be it tools, resources and processes. So, how does this happen with a 92 billion dollar market dedicated to testing and quality assurance?
- But guess what, Quality assurance is compromised… so compromised it cost Delta about 150 million dollars when its computers glitched last summer. And that’s not all for some of the largest airline carriers - since the merger of United and Continental in 2010, their tacked-together IT systems have failed regularly. Bringing to mind the worldwide halt to their airline fleet in 2015. Financial institutions also took a hit. There was the NYSE Technical Glitch that caused a 3.5 hour outage equating to millions of dollars in business and within that very same week the Wall Street Journal crashed. And then there was the infamous failed BATS IPO, when one of the largest equities exchange markets tried to go public on its own platform to find technical glitches preventing the stock from trading. These are major companies suffering grandiose quality issues, proving that yes their quality assurance is compromised and it is creating critical failures at the customer, business level. With that in mind, how did we get here. I am confident that these companies spent the money used some of the most popular test tools on the market, yet, they still faced critical failures. Failures that were not detected during their testing process. Delta – inadequate failover scenario testing NYSE – inconsistent environments LAX - old bugs workaround relating to complex flight plans Knight – recurrent bug that couldn’t be found in testing Bats – incomplete end-to-end testing In terms of technical testing, they applications worked well, but without end-to-end cross functional testing, these “glitches could not be found”
- Automation is just one aspect of testing, and continuing to invest and automate in technical testing will not yield different results. Test automation today still accounts for 20% of testing, most at the UI level- still requires developers. Bottom line test automation has not delivered on its promises
- Testing today is very complex with many variants. IT is not just QA techies sitting in a room testing to see if the code works. Today with organizations working and servicing customers worldwide, IT needs to adapt its testing to mirror the business model in order to ensure quality at go –live. Until now, the initial focus to improve testing is usually mostly on technical testing. This might be due to the fact that this is closer to IT, doesn’t require significant involvement from the Business and it focuses on tools and less on change management. This is suitable and even effective when the goal is to test performance, security, load or regression to some extent. But what about the functional side of the testing? Since it requires more interactions between the business and the IT, is labor intensive both for knowledge gathering and for test execution, functional and business process level testing haven’t been the main focus of improvement so far. NYSE, Delta, BATS exemplify this focus. They didn’t test end-to-end business processes, and experienced failure in production. We believe that to ensure business quality after go-live, it is critical for organizations to shift their testing focus and investment from traditional technical testing to include cross-functional business process testing for full end-to-end business process quality.
- Traditional tools and methodologies are heavy to install, define and maintain. Testers are not anymore only professional testers. Functional analysts and business users are now key stakeholders in the testing process. However traditional tools and methodologies were not designed this new testers and hence the challenge to use office tools to support ever complex testing processes. When using excel or similar workarounds to manage large scale testing cycles, it is very challenging to get real time visibility over the testing progress. It takes time to collect and aggregate the accurate picture and hence it is usually only done daily… if everything goes fine… How can the managers know how things were tested? Should managers really rely on sign off emails and take the risk to go live? If users would have much more time to test, they would document all of their test execution to prove what they tested, how they tested it. Because of a lack of time, and also because this is not really pleasant, no thorough test evidence is created and hence a lack of visibility on test quality and accuracy. Capturing business user knowledge is a challenge: it is labor intensive and requires a lot of coordination. This would have enabled more available resources to perform testing on their behalf. But this is never the right time to do it and even tough customer finally find the time to do it prior a major event in the organization, the business process documentation becomes very fast obsolete Business process testing requires multiple users, each of them with their unique knowhow and authorizations, to go through each end to end business process. Because of a lack of collaboration tools, it is hard to really know when to test and what to test at any point of time. This leads to a lot of idle time between users who need to work sequentially and hence impacts productivity. THE BOTTOM LINE IS – WITH EXISTING METHODOLOGIES AND TOOLS, ORGANIZATIONs STRUGGLE TO DELIVER CONTINUOUS CHANGE AND INNOVATION – WE NEED A NEW APPROACH
- Any business process that requires significant inputs from more than one business "function" is usually considered to be "cross functional". These can be functions from different business units, geographies. Q: are you also performing this type of testing?
- What testing solution are your end users using to report their test results 1 XLS 2 Panaya 3 HP ALM 3 Jira 4 Others
- Panaya's approach to testing, completely transforms testing paradigms by providing an end-to-end testing platform designed for cross functional business process validation that ensures risk-free go live - imperative in a digital world where new business processes must be introduced to market faster. Unlike traditional solutions who focus on test automation for the sake of testing faster, Panaya Test center is focused on testing smarter through test accuracy and acceleration, and user augmentation resulting in 30% reduction in test cycle time. Points to mention Integrated end to end testing: includes both test management, test execution, test documentation and defect management traditional testing tools are generic and mostly focusing on software development Functional testing as opposed to technical testing/performance/load/security testing Even though we cover all the functional test cycles, the UAT (User Acceptance Testing) use case is one of our main differentiators against other solutions
- When we talk to our customers about what makes testing ERP a challenge in a modern software development lifecycle they came back with the following challenges across the planning, execution & management phases. Traditional tools and methodologies are heavy to install, define and maintain. Testers are not anymore only professional testers. Functional analysts and business users are now key stakeholders in the testing process. However traditional tools and methodologies were not designed this new testers and hence the challenge to use office tools to support ever complex testing processes. When using excel or similar workarounds to manage large scale testing cycles, it is very challenging to get real time visibility over the testing progress. It takes time to collect and aggregate the accurate picture and hence it is usually only done daily… if everything goes fine… How can the managers know how things were tested? Should managers really rely on sign off emails and take the risk to go live? If users would have much more time to test, they would document all of their test execution to prove what they tested, how they tested it. Because of a lack of time, and also because this is not really pleasant, no thorough test evidence is created and hence a lack of visibility on test quality and accuracy. Capturing business user knowledge is a challenge: it is labor intensive and requires a lot of coordination. This would have enabled more available resources to perform testing on their behalf. But this is never the right time to do it and even tough customer finally find the time to do it prior a major event in the organization, the business process documentation becomes very fast obsolete Business process testing requires multiple users, each of them with their unique knowhow and authorizations, to go through each end to end business process. Because of a lack of collaboration tools, it is hard to really know when to test and what to test at any point of time. This leads to a lot of idle time between users who need to work sequentially and hence impacts productivity. Are you facing additional challenges in Business Process testing?
- In addition to the previous slides, there are some components that you may want to talk about: Defect management: far more than traditional defect management solutions, Panaya provides out of the box functionalities to best manage defects such as: auto documentation of the defects, system wide defects (prevent the inflation of defects during large scale projects), and a great integration with the testing workflow to better control what can be tested and when. Test execution (Acceleration): we accelerate test acceleration by Automating the testing workflow (“pass the baton”/ “automatic handover between testers”) Automating the creation of test evidence Automation in SAP ERP test execution E-signature: enables regulated customers to sign electronically their test execution. It is not sufficient for strong FDA regulated customers using HP ALM but compared to MS Excel (often used in UAT cycles), that’s a great advantage! Test box = automatic migration of the test scripts Roadmap: Web player: will provide automation also for web applications Release dynamics: will provide scoping insights to the test campaigns Requirement traceability: will enable to import requirements, link to test cases and track traceability/coverage
- As of today we have over 200 global customers across leading verticals including utilities, oil and gas, retail, manufacturing and automotive who have used or are using our testing solution with great feedback on how PTC has helped to increase the quality and reduce the efforts of their testing Earlier we spoke about your upcoming project/business initiatives, so now I would like to take you through the use case of XXX, which covers most of the challenges you will face within this project.
- What is the next improvement that you want to bring to your test strategy 1 – I don’t have a test strategy yet, we should build one 2 – Improve Test Data Management 3 – Get more adoption by business users to our current testing solution 4 – Develop more test automation We will wait a few moments allow everyone to answer the question
- What you see here is a typical process in business applications: Jenny is a key user. Part of her job description is to request and test functionality changes in the Supplier Relationship Management system. Due to segregation of duties and business knowhow, she can only test the creation of a shopping cart and the subsequent purchase order. Then she needs to pass the baton to John to approve the purchase order in the ERP system. From there Peter and Mary will continue the integration test until it is completely passed. Q: are you also performing this type of testing?
- Many customers would actually manage the testing of these business processes with MS-Office documents. Each step describing the activity to be tested at high level together with the team or the tester who need to perform it. Q: is that also the way you describe your business processes?
- A test cycle will usually contain hundreds of such, and therefore this is how the test management platform will looks like. (Some customers may find ways to collaborate on a single file simultaneously but the planning and the execution phases of a test cycle still remain very cumbersome. ) Q: does this look familiar?
- These are the challenges that we identified among our customers, which are managing their testing in this manner They usually complain about the Poor visibility & control they have over testing because it takes a lot of time to collect all the information coming from all these documents and understand where you are in real time They also complain about the Idle time between testers. Even though it might take only few minutes to test each of the transaction it may take hours or even days between the test of two different steps (until the first tester will document the test results and will notify the next tester that he can continue the business process) Also when you ask people to document their own tests and to write down a lot of information that will be helpful for the next tester this requires a lot of Bureaucracy for the users. They will spend a lot of time documenting the process rather than spending time finding defects in the application or validating that the new functionality is delivered correctly Some customers to overcome these type of challenges will actually fly people to the same location in order to perform the testing, which will lead to a certain cost (Time & Cost of flying testers to the same location) in each of the test cycles that is required, and performing these type of activities too often would even lead to a lack of time from the business users. Q: are you also experiencing some of these challenges? Is there any other challenge that you are facing?
- Would you like a Panaya representative to contact you for your own personal demo? We will wait a few moments allow everyone to answer the question…
- Unique Advantages: 100% SaaS: no installation, ready to go. Most of our customers like the ability to consume the service quickly with no setup / preparation whatsoever Quick on boarding: the interface is user friendly and easy to use. The onboarding time of a user is very quick. A casual tester can be up and running with Panaya within 30 minutes. Automated Test Evidence: Panaya provides the ability to document test runs automatically, on the ERP, web applications and all windows applications. Effortless Documentation: business process documentation can be either generated based on actual test evidences or recorded from scratch Intuitive dashboards and reporting: we provide out of the box dashboards and reports to track business process testing (not generic testing progress) Automatic migration of your Word and Excel test scripts: we care about the time it takes you to move from your legacy to Panaya and hence making the migration of your test scripts our problem! (the reasoning behind it is that business process testing has very common patterns which enabled us to build automation around it) Designed for Business Users: Casual business users have never been the main persona covered by traditional testing solutions. Panaya designed the solution to be used by casual users with an easy to use interface, making sure that the onboarding is quick and the user experience is great.
- When we talk to our customers about what makes testing ERP a challenge in a modern software development lifecycle they came back with the following challenges across the planning, execution & management phases. Traditional tools and methodologies are heavy to install, define and maintain. Testers are not anymore only professional testers. Functional analysts and business users are now key stakeholders in the testing process. However traditional tools and methodologies were not designed this new testers and hence the challenge to use office tools to support ever complex testing processes. When using excel or similar workarounds to manage large scale testing cycles, it is very challenging to get real time visibility over the testing progress. It takes time to collect and aggregate the accurate picture and hence it is usually only done daily… if everything goes fine… How can the managers know how things were tested? Should managers really rely on sign off emails and take the risk to go live? If users would have much more time to test, they would document all of their test execution to prove what they tested, how they tested it. Because of a lack of time, and also because this is not really pleasant, no thorough test evidence is created and hence a lack of visibility on test quality and accuracy. Capturing business user knowledge is a challenge: it is labor intensive and requires a lot of coordination. This would have enabled more available resources to perform testing on their behalf. But this is never the right time to do it and even tough customer finally find the time to do it prior a major event in the organization, the business process documentation becomes very fast obsolete Business process testing requires multiple users, each of them with their unique knowhow and authorizations, to go through each end to end business process. Because of a lack of collaboration tools, it is hard to really know when to test and what to test at any point of time. This leads to a lot of idle time between users who need to work sequentially and hence impacts productivity. Are you facing additional challenges in Business Process testing?