Ernst & Young Assurance Consultant Interview Questions, Process, and Tips

Discuss with the developer and provide detailed steps to reproduce the bug.

• Ask the developer to check the environment and configuration settings.

• Provide screenshots and detailed steps to reproduce the bug.

• Collaborate with the developer to find a solution.

• If necessary, escalate the issue to the project manager.

Bug life cycle is the process of identifying, reporting, resolving, and verifying software defects.

• Bug is identified by testers during testing

• Bug is reported to the development team

• Development team resolves the bug

• Bug fix is verified by testers

• Bug is closed if it is fixed or rejected if it is not a valid bug

• Bug can be reopened if it reappears

• Bug life cycle can vary depending on the organization's process

Functional testing is a type of testing that verifies if the software meets the specified requirements.

• It focuses on the functionality of the software

• It is performed to ensure that the software meets the business requirements

• Types of functional testing include unit testing, integration testing, system testing, and acceptance testing

• Examples of functional testing tools include Selenium, HP QuickTest Professional, and IB

I would start by understanding the project requirements and creating a test plan.

• Understand the project requirements and objectives

• Create a test plan based on the requirements

• Identify the test scenarios and test cases

• Execute the test cases and report defects

• Collaborate with the development team to resolve defects

• Continuously improve the testing process

Test scenarios for ATM machine

• Testing card insertion and removal

• Testing PIN entry and validation

• Testing cash withdrawal and balance inquiry

• Testing receipt printing

• Testing network connectivity and response time

Regression testing is testing the entire system after making changes, while retesting is testing only the failed test cases.

• Regression testing ensures that changes made to the system do not affect the existing functionality.

• Retesting is done to ensure that the defects found in the previous cycle have been fixed.

• Regression testing is done after every change, while retesting is done after a defect is fixed.

• Regression tes...read more

Retesting during integration testing ensures that defects have been fixed and new defects have not been introduced.

• Retesting ensures that previously identified defects have been fixed

• Retesting also ensures that new defects have not been introduced during integration testing

• Retesting helps to ensure the overall quality of the software product

Yes, functional testing can be done at any stage of development.

• Functional testing can be done at any stage of development.

• It helps in identifying defects early on in the development cycle.

• It ensures that the software meets the functional requirements.

• Examples of functional testing include unit testing, integration testing, and system testing.

Software testing principles are guidelines that help testers to design and execute effective tests.

• Testing should be planned and systematic

• Testing should be based on requirements and specifications

• Testing should be objective and unbiased

• Testing should be thorough and comprehensive

• Testing should be timely and cost-effective

• Testing should be repeatable and consistent

• Testing should be traceable and auditable

Acceptance testing is a type of testing to ensure that the software meets the customer's requirements. Beta testing is done by end-users.

• Acceptance testing is done to ensure that the software meets the customer's requirements

• It is usually done by the customer or a representative of the customer

• Beta testing is done by end-users to identify any issues before the software is released to the public

• Beta testing is usually d...read more

Scrum roles include Product Owner, Scrum Master, and Development Team.

• Product Owner is responsible for defining and prioritizing the product backlog.

• Scrum Master facilitates the Scrum process and ensures adherence to Scrum principles.

• Development Team is responsible for delivering a potentially releasable product increment at the end of each sprint.

As a tester, my daily routine involves analyzing requirements, creating test cases, executing tests, and reporting defects.

• Analyze requirements to understand the scope of testing

• Create test cases based on requirements and design documents

• Execute tests and report defects using a bug tracking tool

• Collaborate with developers and other stakeholders to resolve issues

• Participate in daily stand-up meetings to discuss progress

V model is a software development model where testing is done at each stage of development.

• It is a sequential process where each stage is completed before moving to the next.

• It has two branches - the left side represents the planning and design phase, while the right side represents the testing phase.

• Testing is done at each stage, ensuring that defects are caught early and fixed.

• It is a popular model for software devel...read more

Agile methodology allows for flexibility, faster delivery, and continuous improvement compared to the rigid and sequential approach of waterfall methodology.

• Agile allows for continuous feedback and adaptation, while waterfall is a linear process

• Agile promotes collaboration and communication between team members and stakeholders

• Agile enables faster delivery of working software in smaller increments

• Agile allows for chang...read more

I wanted to be a software tester because I enjoy finding and fixing bugs, ensuring quality and improving user experience.

• I have a passion for problem-solving and attention to detail, which are essential skills for a software tester.

• I find satisfaction in identifying and resolving issues, ensuring that the software meets the required standards.

• I enjoy the collaborative nature of testing, working closely with developers ...read more

Smoke testing is a preliminary testing to check if the software build is stable enough for further testing.

• It is a quick and shallow testing of critical functionalities

• It is performed after every build to catch major issues early

• It helps in saving time and effort by identifying critical issues early

• It is not a substitute for comprehensive testing

• Example: Checking if the login page is working after a new build

My approach would be to prioritize security and compliance testing, followed by functional and performance testing.

• Conduct security testing to ensure customer data is protected

• Verify compliance with banking regulations and standards

• Test functionality of key features such as account creation and transactions

• Perform load testing to ensure application can handle high traffic

• Test for usability and accessibility for all use...read more