Adglobal360 Softwaretest Engineer Interview Questions, Process, and Tips

Regression testing is testing the existing functionality of the software after making changes to ensure that the changes have not affected the existing functionality. Retesting is testing the same functionality again after fixing the defects found during regression testing.

• Regression testing is done to ensure that the changes made to the software have not affected the existing functionality.

• Retesting is done to ensure ...read more

300 represents multiple choices and 301 represents moved permanently.

• 300 status code represents multiple choices, indicating that the requested resource has multiple representations available.

• 301 status code represents moved permanently, indicating that the requested resource has been permanently moved to a new URL.

• Both status codes are used in HTTP responses to indicate the status of a requested resource.

• Examples of 3...read more

Sanity testing and Smoke testing are types of software testing performed to check the basic functionality of the application.

• Smoke testing is a type of testing that checks whether the critical functionalities of the application are working fine or not.

• Sanity testing is a type of testing that checks whether the bugs reported earlier have been fixed or not.

• Smoke testing is performed after the build is received from the d...read more

Severity is the impact of a defect on the system, while Priority is the order in which defects should be fixed.

• Severity is based on the extent of damage caused by a defect

• Priority is based on the importance of the affected functionality

• High Severity and High Priority defects should be fixed first

• Example: A spelling mistake in a button label has low Severity but high Priority if it affects usability

High priority means the issue needs to be fixed immediately, while low severity means the issue has minimal impact on the system.

• High priority issues are critical and can cause system failure or data loss

• Low severity issues are minor and do not affect the system's functionality

• Example of high priority and low severity issue: A critical security vulnerability is high priority but low severity because it has not yet been...read more

Low priority and high severity refer to the impact and urgency of a bug respectively.

• Low priority bugs are those that do not have a significant impact on the system or user experience, but still need to be fixed eventually.

• High severity bugs are those that have a significant impact on the system or user experience and need to be fixed urgently.

• For example, a low priority bug could be a typo in a non-critical error mess...read more

Agile methodology is an iterative approach to software development that emphasizes flexibility and customer satisfaction.

• Agile values individuals and interactions over processes and tools

• It emphasizes working software over comprehensive documentation

• It encourages collaboration between developers and customers

• It involves breaking down projects into smaller, manageable chunks called sprints

• Examples of Agile methodologies...read more

The test that should be done first is the one that covers the most critical and high-risk functionality.

• Identify critical and high-risk functionality

• Prioritize tests based on risk

• Perform tests in a logical order

• Re-evaluate test priorities as development progresses