Axeno Software Engineer Interview Questions, Process, and Tips for Experienced

STLC stands for Software Testing Life Cycle. It is a process followed to ensure quality in software development.

• STLC involves planning, designing, executing, and reporting of tests.

• It includes various stages like requirement analysis, test planning, test case development, test execution, and test closure.

• The main objective of STLC is to identify defects early in the development cycle and ensure that the software meets ...read more

Defect life cycle is the process of identifying, reporting, prioritizing, fixing, and verifying defects in software.

• Defect is identified by testing or user feedback

• Defect is reported to the development team

• Defect is prioritized based on severity and impact

• Defect is fixed by the development team

• Defect fix is verified by testing

• Defect is closed if verified or reopened if not fixed

Regression testing is the process of testing changes made to a software application to ensure that existing functionality still works.

• It is performed after making changes to the software

• It ensures that existing functionality is not affected by the changes

• It helps to catch any defects or bugs introduced by the changes

• It can be automated to save time and effort

• Examples include testing after bug fixes, new feature additio

Sanity testing is a type of software testing that checks whether the basic functionalities of the application are working properly or not.

• It is performed after the completion of functional testing

• It is a subset of regression testing

• It helps to identify the defects early in the testing cycle

• It is a quick and shallow testing process

• Example: Checking if the login page is working properly

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

• It is a quick and shallow testing technique

• It is performed to ensure that the critical functionalities of the software are working fine

• It is usually done after a new build is deployed

• It helps to identify major issues early in the testing cycle

• It is not a substitute for comprehensive testing

Priority and severity are used to classify issues based on their impact and urgency.

• Priority refers to the urgency of fixing an issue, while severity refers to the impact of the issue on the system or users.

• Priority is usually assigned based on the business needs and impact on the project timeline.

• Severity is usually assigned based on the impact on the system or users, such as critical, major, minor, or cosmetic.

• For ex...read more