API Automation

Question 1

What is SOAP UI?

Answer 1

SOAP UI is a free, open source cross-platform functional Testing solution. It enables you to rapidly and easily create and execute automated regression, compliance, functional and load tests. Its used for Web Services Testing

Example: SOAP UI is commonly used by software testers to automate testing of web services.

Question 2

What is soap ui

Answer 2

SoapUI is a desktop application that helps developers and testers test APIs, web services, and back-end services allows you to easily and rapidly create and execute automated functional, regression, and load tests

Question 3

What kinds of test would I run on soap uI

Answer 3

Functional test
Load test
Regression
Performance

Question 4

If you ran a script in automation w 500 test how to you track the ones that failed?

Answer 4

Use a Test Framework: Utilize a framework like JUnit or TestNG, which supports detailed reporting.
JUnit: Use @Test annotations and check the generated reports or logs for test outcomes.
TestNG: Integrate with TestNG’s XML or HTML reports for detailed failure information.
Integrate Reporting Tools: Enhance reporting with tools like ExtentReports
ExtentReports: Provides a comprehensive HTML report with pass/fail details and logs.
Implement Logging: Use SLF4J with Logback or Log4j to log detailed error messages and stack traces when tests fail.

Review Reports: After test execution, analyze the generated reports to identify which tests failed and investigate the issues.
This approach ensures you have a structured way to track, log, and report on test failures effectively.

Question 5

Different types of asserts and what do they do?

Answer 5

Hard assert halts the test when one test failed

Soft assert continues and reports failed tests at the end

Assert.assurttrue
Assert.assertequals

Question 6

Implicate and explicit waits explain what they are?

Answer 6

implicit” and “explicit” waits are techniques used to handle timing issues and ensure that elements on a web page are loaded and ready for interaction

Implicit waits apply to all elements in the WebDriver instance, while explicit waits are specific to particular conditions or elements.

Explicit waits are more precise and are applied only to specific elements or conditions.
They allow you to wait for certain conditions to be true before proceeding. For example, waiting until an element becomes visible or clickable.