solution, guides to creating processes and objects are available elsewhere on the Blue Prism portal. Objects from the ODI should be developed first and then the processes. As there are typically multiple objects multiple developers can be involved in object development. Only one developer at a time however can work on a process. Blue Prism process templates should be used when creating Blue Prism Processes. During the implementation of the Blue Prism Framework a local design authority will be agreed that will govern design control and development best practise. Peer review is essential at regular stages of the development phase to ensure development quality. At the end of each object and process development task unit or configuration testing is performed by the developer. Reference A Blue Prism release of a completed solution containing processes, objects, work queues, environment variables and report templates is available for download from the Blue Prism Portal
[email protected] • +44 (0)870 879 3000 • Centrix House, Crow Lane East, Newton-le-Willows, WA12 9UY Commercial In Confidence The Operational Agility Software Company 6 Test As the terminology used to describe test phases can differ from client to client, this document will use generic terms in an attempt to avoid any potential misunderstanding of terms like validation, verification, live proving and UAT. The following phases form the starting point from which a local test approach is agreed during the Blue Prism Framework implementation. The agility of the Blue Prism platform allows for testing to take place during development. Only when you get to test phase 3 are developers no longer involved. Phase 1 Performed by – Blue Prism developer, Blue Prism tester and client SME (optional) Blue Prism running mode – Process Studio and Control Room Blue Prism environment – Development Target System environment – Test Acceptance criteria – Test script In this phase the tester/SME and the developer work together to prove that the solution conforms to the captured process definition (PDD). Scenarios are created by the tester in the test environment that validate the process along the various process paths. Starting in Blue Prism process studio cases are stepped through and as confidence in the solution increases the process speed can be increased until eventually the process is running at full speed. At this point case processing time estimates can be provided. This is the stage where the quality of the PDD comes to light. Both the SME’s test script and the developer’s work are based on the original process definition, and if that definition is accurate and comprehensive then this test phase should run smoothly. However new scenarios not mentioned in the PDD may be encountered at this stage. If this happens, testing may need to stop while a resolution for the scenario is identified, the development is changed and documentation updated.
You've reached the end of your free preview.
Want to read all 14 pages?
- Summer '09
- ramana rao
- Chemical Engineering, Blue Prism