Sample Mock interview.
General
What is your day to day routine?
We have daily stand-ups and defect meetings where we discuss the defects and get status of the defects.
Attend meetings for business requirements and then plan our test plan.
Based on requirements , we add/update our test cases. Once any feature is deployed on UAT, we test the application.
Work with developers on testing in dev environment.
I get involved in PVT testing after any deployments.
Can you tell me on Mock stubs or have you used it.
Mocks are dummy json responses that are used to test the code when actual application is not ready.
We have a mock environment where we create mock data files and then ask developers to point to that.
We are using wiremock as mock server.
SDLC/ AGILE
What is SDLC?
SDLC – Software Development Life Cycle is a overall process of project delivery from start to end.
Waterfall vs Agile
Waterfall is an older pattern used by many companies. Here the project goes for months. In the beginning stakeholders will
come up with design and then developers will work on full project work and then testers will work. Here the overall cycle could be around 6 months and stakeholders
will see the final product after that. It’s very hard to do any changes at that time.
In Agile, we have sprints , which are generally 2/3/4 weeks and a small portion of the work gets delivered step by step.
LOAD TESTING/ JMETER
What are the common used load testing tool
Jmeter
Fiddler
How Jmeter is used
JMeter acts like a group of users sending requests to a target server.
It collects response from the target server and other statistics which show the performance of the application.
How were you using JMeter?
We have few APIs used by clients and before any new production deployment , we used to have load testing of that.
In JMeter, we have a test plan where we simulate a x number of concurrent users to verify the load and we make sure it has minimium required TPS (Threads per second),
which is minmium 200 TPS for our project.
API TESTING/ POSTMAN
Common tools/softwares used for API Testing :
– Soap UI
– Postman
What is API?
API stands for Application Programming Interface. It means an interface /method /way where in two different softwares communicate with each other.
Difference between UI testing and API testing
In UI testing, we actually test the graphical interface and test various web elements like fonts, text , images , etc.
In API testing, we validates that the application API / service provides the proper data/response when a given request is passed.
Have you API testing?
The application has various REST APIs which are consumed by other internal apps and clients.
We generally test these APIs using Postman.
What do we test in APIs?
We test the accuracy of the data.
Most of the APIs are GET requests where based on the inputs, we get response, mainly JSON.
We verify if the JSON data is valid, the values are correct.
We sometimes connect to database and verify if the API response is based on data.
What are the common HTTP codes in APIs?
For success response, we get 200.
For generic error, we get 500,
404 if the resource is not found
401 if there is authorization issue.
What is the authorization mechanism followed to hit API?
All API are protected using API gateway and we use OAUTH Tokens. We first call a token url passing client id and client secret and gets access token in response.
We pass the same access token as header to the actual API.
SELENIUM
what is the most challenging thing you found in selenium?
Many a times there is no ID or simple way to get the element, or websites having dynamic content generation where in IDs or xpath keeps on changing.
And sometimes there are pop ups /layovers
REPORTING
What do you use as part of reporting?
I export the defects from JIRA and email the list to our team on daily basis.
Our automated regression suite runs daily and sends report email to our team.
DEBUGGING
How do you debug if a defect is associated to which team/developer?
If there are front end , UI alignment issues or some elements not looking proper ,then it’s directly a front end team defect.
We also sometimes verifies in different browsers and incognito mode.
If there is a data not coming and it used a backend API, then we can see the response of backend API using browser developer tools /inspect element.
If API has failed or bad response , then we can assign it to the API developer team.
We also sometimes verify in logs. All the application logs goes into SPLUNK.
We log in to splunk and based on user id, correlation id, we see logs and can guess the defect cause.