1. Automated tests CustomWare.Net

2. Goals Quality Finding problems before delivering Stability Upgrade projects Downgrade Refactoring Deacreasing of manual work Automated execution of the tests during each night

3. General approach Integration tests GUI Service DataBase Integration tests Fake

4. Tools Team foundation server Build workflow Visual Studio 2012 MS fakes Unit tests MS SQL Server SQL Server Data Tools UI Testing Ranorex

5. GUI Testing - WinForms Predefined values Value Emulates user activity Fake service layer isolates DB and service Test cases

6. GUI Testing – WPF Values Fake service layer isolates DB and service Presentation logic Test cases Predefined values Unit tests Parameterization

7. GUI testing UI Tests – C# scripts to test WinForms\WPF applications Base forms Client registration Contract registration Business processes (CA Deposit and etc) Unit testing – developing of c# tests to cover isolated from UI parts of business logic Various helpers Various embedded algorithms IBAN checker TaxCode checker Etc.

8. Service testing Parser and conditions Business Process steps skips and AutoExec Transaction templates BP Mapper (TPFeed, file upload, new swift reader etc.) Serialization(algorithm of interchange of the objects between service and client) Transaction parsing BP saving Contract saving Client transaction handling Payment plan generation Service jobs Core engine(scheduling, parallel executions chains etc.)

9. DB testing Critical SPs Entry add Pending debts for loans Transaction template search Contract registration Account generation Search engines Saving of base objects Jobs Checking of calculation logic Interest accruals Setting overdue etc. Business integrity checking Account balances vs account sign Fund reservation Repayments and payment plans vs accounts Payment plans

10. Integration tests Integration testing is the phase in software in which individual software modules are combined and tested as a group

11. Testing balance Coverage by tests Solution complexity and maintainability

12. Areas of responsibilities UI testing- RO DB testing – core development Service – core development

13. Continuous integration DB Project Deployment Building of the version Layers testing (DB, Service and UI separately) Integration tests Reports

14. Current status Sample unit tests were created, with help of MS Fakes Testing of parser and cw.net expressions engine Testing of base view model for dynamic UI Team foundation server, was proved to be a platform Investigation of build workflows and team foundation activities Parameters for continuous integration Ability to execute automated tests Automated UI Ranorex – tested under cw.net.

15. Example Out of the box build workflow Building of cw.net under TFS Running of unit tests CW.NET conditions Service layer is isolated by MS Fakes Reports checking

16. Further steps Finalization of selection of the tools Installation of test laboratory environment under TFS Build machine Build workflows Establishing of conceptual technical part Pilot project – PCB GEO upgrade to latest release Developing of unit tests to cover fundamental system functionalities Step by step developing of automated GUI tests Final goal to have continuous integration solution at the end of the project with partial unit tests covering

17. The End