10+ Tanglin Developments Interview Questions and Answers

I would analyze the defect, prioritize it based on severity, communicate with the development team, and work on fixing it promptly.

• Analyze the defect to understand the root cause

• Prioritize the defect based on severity and impact on the customer

• Communicate with the development team to discuss the defect and potential solutions

• Work on fixing the defect promptly to ensure customer satisfaction

Discuss with the developer to understand their perspective and provide additional information or evidence to support the bug report.

• Initiate a discussion with the developer to understand their reasoning for not accepting the bug.

• Provide additional information or evidence to support the bug report, such as screenshots, logs, or test cases.

• Collaborate with the developer to reproduce the issue and demonstrate the bug in action.

• Seek input from other team members or stakeholders t...read more

I would gather information from stakeholders, previous test cases, and the application itself to write test cases without documents.

• Consult with stakeholders to gather requirements and functionality details

• Review previous test cases and test plans for similar features

• Explore the application to understand its functionality and potential areas for testing

• Use experience and knowledge of testing best practices to create comprehensive test cases

I will cover various types of testing including functional, non-functional, manual, automated, regression, performance, security, and usability testing.

• Functional testing - ensuring the software functions correctly according to requirements

• Non-functional testing - testing aspects like performance, security, and usability

• Manual testing - testing performed manually by testers

• Automated testing - using tools to automate test cases

• Regression testing - testing to ensure new code ch...read more

Requirement Traceability Matrix is a document that links requirements throughout the validation process.

• It is used to ensure that all requirements are met during testing.

• It helps in tracking the progress of requirements from inception to implementation.

• It provides a way to trace back to the source of each requirement.

• Example: If a specific requirement fails during testing, the matrix helps in identifying the source of that requirement.

Regression testing is the process of retesting a software application to ensure that new code changes have not adversely affected existing functionality.

• Performed after code changes to ensure that existing features still work correctly

• Helps in identifying any defects introduced by new code changes

• Automated tools can be used to streamline the regression testing process

Severity priority is a way to classify and prioritize issues based on their impact and urgency.

• Severity refers to the impact of an issue on the system or users

• Priority refers to the urgency of fixing the issue

• Issues with high severity and high priority should be addressed first

• Examples: A critical bug that causes system crashes would have high severity and priority

• Examples: A minor cosmetic issue may have low severity and priority

Smoke testing is a quick test to check if the build is stable, while sanity testing is a subset of regression testing to verify specific functionalities.

• Smoke testing is done to ensure the critical functionalities of the application are working fine after a new build.

• Sanity testing is performed to verify that the specific changes made in the code are working as expected.

• Smoke testing is a subset of acceptance testing, while sanity testing is a subset of regression testing.

• Smo...read more

Dynamic xpath is a technique used in test automation to locate web elements based on changing attributes or properties.

• Dynamic xpath is useful when the attributes or properties of web elements are not static

• It allows testers to write flexible and robust test scripts

• Dynamic xpath can be used to handle scenarios where web elements have dynamic IDs, classes, or other attributes

• It helps in maintaining test scripts when the structure of the web page changes

Testing types include functional, non-functional, manual, automated, regression, performance, and security testing.

• Functional testing ensures that the software functions correctly according to the requirements.

• Non-functional testing focuses on aspects like performance, usability, and security.

• Manual testing involves testers executing test cases manually without automation tools.

• Automated testing uses tools to automate the execution of test cases.

• Regression testing checks if n...read more

UAT testing stands for User Acceptance Testing, where end users validate the system before it goes live.

• UAT testing is the final phase of testing before the system is released to end users.

• It involves real users testing the system to ensure it meets their requirements.

• UAT testing helps identify any issues or bugs that were missed during earlier testing phases.

• It is crucial for ensuring the system is user-friendly and meets business needs.

• Examples: End users testing a new soft...read more

Agile methodology is a project management approach that emphasizes flexibility, collaboration, and iterative development.

• Agile focuses on delivering working software in short, iterative cycles called sprints.

• It values customer collaboration and responding to change over following a strict plan.

• Teams work closely together and adapt to feedback throughout the development process.

• Common Agile frameworks include Scrum, Kanban, and Extreme Programming (XP).

Bug life cycle involves identification, reporting, fixing, retesting, and closing of a software bug.

• Bug identification: Finding and documenting the bug.

• Bug reporting: Informing the development team about the bug.

• Bug fixing: Resolving the bug by developers.

• Bug retesting: Verifying if the bug is fixed.

• Bug closing: Marking the bug as resolved.

• Example: A tester finds a login issue, reports it to developers, they fix it, tester retests, and finally closes the bug.