Task 14 Automation Testing

Q1.A1.

Q2.A2. Some of the common automation tools are Selenium, Appium, TestNG, Cucumber etc...

Selenium: Selenium is an Open Source tool used for Automation Testing. Selenium is widely used for testing Web Applications with support for various programming languages like Python, Java, and Ruby. With Selenium you get access to numerous testing abilities. These include Regression testing, Functional Testing, Compatibility Testing, and much more.

Appium: Appium is an open -source, popular tool that must be included in this automation testing tool list. It is used to test native, hybrid, and mobile web apps. It would drive Android, iOS, and Windows apps that use the WebDriver protocol.

TestNG: TestNG is one of the best multi-purpose automation testing tools, where NG stands for “Next Generation” and makes the best use of annotations (@), thanks to its inspiration from JUnit. With TestNG, you can extend the UI testing into E2E and integration testing. Thus, TestNG facilitates the easier conduct of end-to-end testing.

Cucumber: Cucumber is a commonly used testing tool supporting Behavior Driven Development (BDD). Write more understandable tests with no regard to technical knowledge. As for BDD, product owners and business analysts would write acceptance tests or test scenarios to enact the system behavior from a business perspective.

Q3.A3. The practice of testing websites on various browsers, known as cross browser testing, ensures compatibility across different web browsers for websites and web apps. It is crucial for ensuring all components, including text and multimedia, perform seamlessly, contributing to an excellent user experience.This testing form, categorized under non-functional testing, aims to verify the proper functionality of website elements across various browser versions. It encompasses checking HTML, JavaScript, plugins, and design elements to ensure consistent appearance and behavior across browsers.

Q4.A4. TDD: Test-driven development typically involves writing a test for a certain piece of functionality, running the test to see it fail and then writing the code to make the test pass. That way, developers can be confident that they’ve written code that does the job and other developers reusing components can run the test to be confident that their own code will properly function.

BDD: Behavior-driven development typically involves a developer, test engineer and a product manager (and potentially other stakeholders). The group meets to come up with concrete examples of acceptance criteria in a user story. These examples are described using a domain-specific language, like Gherkin, and put into a feature file. The feature file is converted into an executable specification where developers can then write an actual executable test.