about me

 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

test data -- test execution- test metrics - exit criteria

manually,
mass copy of dat afrom prod environemt
mass copy of dat afrom legacy client system
automated test data eneration tools like dtm
prepare test data for performave test-live simulated data
chekc for authorisations, confidentiality, encryprtion,
using ecp,bva,no data

test metrics:

% ge of passed test cases  vs. test cases executed
defect density
critical defects %ge
to givve a clear idea of testing attach test execution results, defect reports

test execution report:  test cases planned and executed
pass, fail?
critical defects?
any envi down issues
show stoppers
dependancies


exit criteria:
100% test cases executd
95% pass, no open critical, all remaining agreed to releae in next release
all test metrics collected, defects logged
sign off

best practices - process improvement

follow the processes indicated by cmmi and iso quality standards in order to gain customer faith and satisfaction
always document the qa policies and methods
perform both static and dynamic testing
perform both +ve and _ve testing
trace the req to map the test components and db for test coverage
perform thourough regression
select the tools which best support thr process
metrics: always keep track of the test and defect metrics

static: check req specification, design doc, test plan review, test case walk though, scripts, help docs, web page content etc...verification

dynamic: validation
functional and non functional
unit, integration, system...  load, security, db
iso cmmi levels


process improvemnt:

make a list of what r the issues encountered in last project
testing cost is lot more than expected- analyse where the money spent went worng..use opensource tools insted, cut down soem costs
less time: dev delivered code very late- qa had hardly time to check the app- talk to dev team about the deleverables
team members joined late-took some time to get them on board
last min defects: clarify the req with business in early stages and develop good domain knowlege before start of test
better to work in small teams

testplan-defect-test case

Test plan: rule book 
helps in determining the testing effort needed to validate application
people outside qa dev, business , cust know the details of testing

objective
scope: features to be tetsed not
resources
deleivery schedule
approach
tools
kind of test process-types of testing
assumptions-dependancies
test data
risks and mitigations
exit criteria
defect tracking


defect:  description, step by step how to reproduce it and defect id, envi, seve, module, project, status

test case: document  that with a given data and initial conditions, the step by step execution of user actions and expected result.

many test case strategies:

BVA: check for boundaries , corner case  for a text fireld designed to enter 1-10
  boundaries : 0,1,10,11
ECP: devide in to partitions of valid and invalid data:
valid: 1,5,10   invalid:  -1,12
state transition:   result of different sets of data like cc, home  cf, login invalid  ee error msg,

decision table: combination of data in a chart like login functionality
login               c as correct   f as false data
                       c f,    c blank,  f c,  f blank,  blank blank, f f, c c, blank,c   blank,f
password    
 9 combinations..

error guessing


Use case testing: test with system and actor with d/f operations..
Static testing: Code review , inspections ,walkthroughs , technical review are some static testing methods.

alm

managment tool:

mgt  tab: release specification module: create and manage release cycles- relese cycle, scope, milestones etc

requirements: keep req's functional.non functionl- create req tracebility
view -coverage analysis
test plan modul:  test cases
test lab module
defects
dash board:  graphs ,project reports   view analysis
coverage graph,process
summary graphh

my sql

My sql work bench

inner join,
self join, : from same tables
outer join

inner: all the matching information from two tables
left outer: all the information from left table+ matching information from right table


select e.emp_id, e.hire date ,m.lastname
from emp e left outer join location m              equi join
on e.empid=m.location id
and e.lastname=;xxx'


select e.emp_id, e.hire date ,m.lastname
from emp e left outer join emp m
on e.empid  >  m.location id                               non equi join
and e.lastname=;xxx'



group by:

avg, wont count null, so use nvl


select max(salary), deptid,jobid,count(jobid)
from employee
groupby deptid,jobid
orderby deptid

having max(salary)>6000

severity and priority

priority: the order in which the defect need to be addressed and resolved

severity: the impact of the defect on the system

high prio, low sev:  copany name mispelled in main page

low pri, high sev:  clciking on one of the hidden link leads to server crash, but the probability of cliking is less..

high prio, high sev- login function not working
low prio, low sev:  cosmotic errors

defect triage: a formal meeting, when there r so many defcts and less resources to fix, team has to evalaute and assign them based on priority and severity

Happy Path - quality

Happy Path: test case is executed successfully with given input and out put the expected result with out any errors.

making sure application showing error when it is supposed to and not throwing error when it is not supposed to

-ve :  with intention of finding error, checking weather application giving error when it is not supposed to.. test with data the application not designed to handle such..

Quality:  Meeting the needs and expectations of a customer wrt functionality,design,reliability and price

Assuarance: positive declaration on a product or service..A guarantee that prod will work


Test cases design : bva- test cases are generated using the extremes of the input domain. maiainly focus on corners, lower boundary and upper boundary..

, ecp- divide test input  in partitions-valid and invalid data
valid invalid, decision table, error guessing, state transition,

Bread toaster example

User Manual: How the functionality work
Functionality: Put bread and make sure it is toasted and pop out
ecp: max time, min time,,
bva: max no.of breads, no bread,
usability: how easy it is
performance:
security:powe consumption, out put voltage, surface heat
look and feel: how is the out come of bread under d/f conditions...,
the product duarability, color, specification, buttons,
compatibility: type of bread and response
stress :  pushing buttons agaiun and agian..
4 bread s at a time,,and see the response..2 breads,

personal qns

personal interview qns

1.What interest you most in this job?

Most of my QA experinece was wih financial domain.persoanlly, I am very much interested finacial sector.My experience and domain knowledge will help me to perform the best in your organisation too..
This is similar type of working environment and responsibilities.I believe this opportunity helps me develop further in my career as well

2.why you are in QA?

i believe Nothing is perfect in this world other than god's creation. especially in software world, because of work pressures,time deadlines, complexity no product is perfect when it is created. Company's reputation depends on quality of products or services they delivered.

Qa  testers are the final judges to give the guarantee that the  product works as expected.

  It is very interesting and challenging for me as it needs many skills including attention to every small detail,good cooperation with all teams,strong desire for quality

3.DO you have any questions?

What kind of qa processes and testing tools you are using?
what would be my role and responsibilities of a successful candidate for this position..

work environment,project details-what project i would be working on?

what is the regular day to day work for a qa

4.y should we hire you?

i have more than 7 years of qa experience in testing complex web a/ps

i have very good knowledge of sdlc and stlc end to end testing and defect tracking

very strong  sql experience for checking the correctness of data

expertise in req analysis, test plan,test case design , and test metrics reports

experience in agile environment 

I am self motivated, quick learner and quickly adopt to new environments,

good organise skills and good team player..

proven record of delivering projects successfully on time

very good financial domain knowledge, done bachelors in engineering

5.Best strengths and weekness?

I am a continuous learner have very positive attitude and easily adopt to new environments

Strong knowledge in end to end testing and many  open source tools

weakness: i used to be  little nervous to speak in front of crowd..but i  overcome it slowly by  participate  more  in meeting conversations and share my views 

6.professional achievement

i joined as qa manual tester and then learned java wrote sun certification.

In visa, i setup the whole automation setup by myself.I handled the sv project so well in wells, i got recognised for my hardwork and got award for my contribution

7.how u r collegues describe u?

i am dependable, hard working and easy going...

8.how u deal pressure?

i will keep quite and calm..take deep breath and do meditation . write down all the tasks i need to do..prioritise them and take help from team if needed.talk to lead if required.

9. what if no time..
I will communicate with my mgr and explain him what projects I am working on, how much time it takes and deleivery schedules,  if that doesn't work
I will priortise my tasks based on risk analysis
I will first test the functionalities which have high security  and fiancial impact, which features are highly visible ,based on prior experiences test the functionality which i think has more chances of errors,

10. who is responsible for quality

everyone who is part of work resposible for quality however mainly the organisation is responsible for it, as the mgt has to monitor the quality standards in all stages of developing the product by providing  good resources, tools, domain knowledge trainings, and making sure the standards are following in all the departments

11. customer service comes under quality?
yes, In my opinion, quality means customer satisfaction.
company has to make sure the product they delivered should meet the customer expectation in all stages.after delivery of product customer may need help in installation, any trouble shooting,

12. most challenging situation:

whenever i change company, i have to adopt to new environment, use d/f test management tools which is bit challenging. In my last project validating the wire transfer in production environment i feel bit challenging as to get data and working with various teams in order for the wire to go through