CMS IT Services Interview Questions and Answers

Integration testing checks if different modules work together, Black box testing checks functionality without knowing code, Regression testing checks if changes affect existing functionality.

• Integration testing verifies if different modules work together as expected

• Black box testing checks functionality without knowing the code

• Regression testing checks if changes affect existing functionality

• Integration testing is done after unit testing and before system testing

• Black box tes...read more

Retesting is testing the same functionality again after fixing the defects while regression testing is testing the entire system after making changes to ensure that the changes did not affect the existing functionality.

• Retesting is done to ensure that the defects reported earlier have been fixed.

• Regression testing is done to ensure that the changes made to the system did not affect the existing functionality.

• Retesting is a subset of regression testing.

• Regression testing is ti...read more

Smoke testing is a quick and shallow test to check if the basic functionalities of the application are working. Sanity testing is a more thorough test to check if the major functionalities of the application are working after changes have been made.

• Smoke testing is done to check if the application is stable enough for further testing.

• Sanity testing is done to check if the changes made to the application have not affected the major functionalities.

• Smoke testing is a subset of ...read more

HTTP is unsecured while HTTPS is secured with SSL/TLS encryption.

• HTTP stands for Hypertext Transfer Protocol while HTTPS stands for Hypertext Transfer Protocol Secure.

• HTTP operates on port 80 while HTTPS operates on port 443.

• HTTP is vulnerable to attacks while HTTPS is secure due to SSL/TLS encryption.

• HTTPS is used for secure online transactions such as online banking, e-commerce, etc.

Test cases ensure software quality. They should be comprehensive, clear, and repeatable.

• Identify test scenarios and objectives

• Create test cases with clear steps and expected results

• Ensure test cases cover all functional and non-functional requirements

• Execute test cases and report any defects found

• Update test cases as needed based on changes to the software