i have 7 years of qa experience testing different complex web applications on different domains,mostly in financial domain.I have done bachelors in engineering from india.
I have expertise in sdlc ,testing methodologies include waterfall and agile environments
I have strong sql skills and had expertise in req analysis, creating test deliverables,test mgt and defect tracking tools.
i like exploring open source tools and i consider myself as a continuos learner and quicly adoptive to new environments.
My last project with wells fargo, and before that i worked in visa.
Wells fargo: I worked in wholesale commercial banking application names ceo portal, its a single sign on web application for all the company financial needs.when user login to portal, user can access all the services he is enrolled for..like account balances, ach payments, check transfers, stop payments etc. wellsfargo also provides wire transfer facility for commercial customers.
for the protection of customers money from fraudulant activities, wells implement many features in which dual custody is one, it needs an one more person approval in order for a transfer of funds or any admin changes in addition to rsa token.so in a company , if user1 initiate a wire it will come in to wires queue panel waiting for user2's approval.qa has to play 4 roles as a company admin who have all permissions to create, view, approve/reject and set the daily thresholds, give authorisations to users, user1 have only create permissions, user2 with approve permissions, user3 with no permissions etc...there is like user can create free form wire/one time wire or create a template with a fixed benificiary and recurrent money payment like rent. there r many type of wires domestic, book transfer, drawdown, international, irft, etc
i also worked on another security feature, which is oobv/sv , this comes into picture when user decline to dual custody..sv works by using telephonic channel by delevering a code to voice message text msg to pre enrolled phone number.here qa has to test with users ready for sv, and add a phone number and make sure once enrolled getting code and once phone is added to system, user is enrolled and user have options to add another ph, disable the existing
I have expertise in sdlc ,testing methodologies include waterfall and agile environments
I have strong sql skills and had expertise in req analysis, creating test deliverables,test mgt and defect tracking tools.
i like exploring open source tools and i consider myself as a continuos learner and quicly adoptive to new environments.
My last project with wells fargo, and before that i worked in visa.
Wells fargo: I worked in wholesale commercial banking application names ceo portal, its a single sign on web application for all the company financial needs.when user login to portal, user can access all the services he is enrolled for..like account balances, ach payments, check transfers, stop payments etc. wellsfargo also provides wire transfer facility for commercial customers.
for the protection of customers money from fraudulant activities, wells implement many features in which dual custody is one, it needs an one more person approval in order for a transfer of funds or any admin changes in addition to rsa token.so in a company , if user1 initiate a wire it will come in to wires queue panel waiting for user2's approval.qa has to play 4 roles as a company admin who have all permissions to create, view, approve/reject and set the daily thresholds, give authorisations to users, user1 have only create permissions, user2 with approve permissions, user3 with no permissions etc...there is like user can create free form wire/one time wire or create a template with a fixed benificiary and recurrent money payment like rent. there r many type of wires domestic, book transfer, drawdown, international, irft, etc
i also worked on another security feature, which is oobv/sv , this comes into picture when user decline to dual custody..sv works by using telephonic channel by delevering a code to voice message text msg to pre enrolled phone number.here qa has to test with users ready for sv, and add a phone number and make sure once enrolled getting code and once phone is added to system, user is enrolled and user have options to add another ph, disable the existing
No comments:
Post a Comment