Notes

8/13/15

Notes from the meeting

1. Identifying Automation tc's
2. On local machine
3. On remote machine(where informatica is running)
4. From 2016 focus is on CD
5. GCOT university had session on CD
6. CD - Test, builld and release
7. Software on local machine vs server (software could be Excel, word or informatica)
8. Structure of CD framework
9. dev could be focused on development rest will be automated
Code moving to test environment, tested and deployed
10. CD is related to server???
11. no struggle in build automation, but problem is with setting up platform for regression
12. We have implemented a solution for informatica testing in OFSAA regression test automation.
In this solutions we require the informatica client to be installed on the machine where we are executing our regression test automation.

This solution will not work when your platform will be onboarded on CD because in CD the test automation scripts are executed on ALM servers and these servers has the capability to execute only web based applications.

For long term solutions either your team can create a solution to start informatica jobs without manual intervention which will not require the test automation scripts or we can work on a enterprise solution.

Looks like on client machine, following could be the structure:

HP ALM -> UFT -> Informatica -> DB

UFT -> DB: UFT connects to DB, but we need informatica because it does ETL(Extract, Transform and Load) to DB.

If we are using the scripts in server level(CD), then scripts may not access Informatica as scripts could only access Web Applications at server level.