WNS Interview Questions and Answers

Upon receiving a build, I will follow a structured process to ensure thorough testing and validation.

• Review the release notes and requirements to understand the changes and features included in the build

• Create test cases based on the requirements and prioritize them based on criticality

• Execute test cases manually or using automation tools to validate the build

• Report any defects found during testing and work with developers to resolve them

• Perform regression testing to ensure e...read more

Unit test case for ATM withdraw and removing duplicates from a string, and writing a post request using RestSharper.

• For ATM withdraw, test if the correct amount is deducted from the account balance

• For removing duplicates from a string, test if the output string has no duplicate characters

• For writing a post request using RestSharper, test if the request is successful and returns the expected response

Yes, I am ready to accept the offer letter.

• I am excited about the opportunity and ready to take on the responsibilities of a Senior Test Engineer.

• I have thoroughly researched the company and believe it aligns with my career goals.

• I have discussed the offer with my family and they are supportive of my decision.

• I am confident in my skills and experience to excel in this role.

• I am ready to negotiate and finalize the details of the offer.

My expected CTC is based on my experience, skills, industry standards, and the responsibilities of the role.

• My expected CTC is in line with industry standards for Senior Test Engineers.

• I have taken into consideration my years of experience in testing and quality assurance.

• I have also factored in the specific responsibilities and requirements of the Senior Test Engineer role.

• I am open to negotiation based on the overall compensation package offered by the company.

Bug life cycle is the process of a bug from identification to resolution.

• Bug is identified by tester

• Bug is reported in bug tracking system

• Bug is assigned to developer

• Developer fixes the bug

• Bug is retested by tester

• Bug is closed if fixed or reopened if not

Types of testing include functional testing, non-functional testing, manual testing, automated testing, and regression testing.

• Functional Testing: Testing the functionality of the software against the requirements.

• Non-Functional Testing: Testing aspects like performance, usability, and security.

• Manual Testing: Testing performed manually by testers without the use of automation tools.

• Automated Testing: Testing performed using automation tools to increase efficiency and accurac...read more

Sanity testing is a subset of regression testing that focuses on testing the most crucial functionalities of a software application.

• Sanity testing is a quick and focused testing to ensure that the most critical features of the application are working correctly.

• It is usually performed after a minor change in the code or functionality to check if the core functionalities are not broken.

• Sanity testing is not exhaustive like regression testing but aims to quickly validate the sta...read more

Smoke testing is a preliminary testing to check if the basic functionalities of a software application are working fine.

• Smoke testing is a quick and shallow testing of the critical functionalities of an application.

• It is usually done before more in-depth testing to ensure the application is stable enough for further testing.

• Smoke testing helps in identifying major issues early in the development cycle.

• Examples of smoke tests include checking if the application launches succes...read more