Selenium WebDriver Advanced - Industry Standard Framework - Problems of a No Framework Test Case

The video tutorial discusses the problems with a current login test class, highlighting issues such as excessive length, redundancy, and lack of readability. It emphasizes the misuse of WebDriver APIs within test methods, citing Simon Stewart's advice. Solutions include creating separate page classes to handle actions and improve code readability. The tutorial also stresses the importance of keeping assertions within test methods, ensuring clarity and maintainability in larger applications.

What is one of the main issues with the current test class?

• It is too short.

• It lacks any redundancy.

• It uses too many different programming languages.

• It is too long and not very readable.

Why is using Webdriver APIs directly in test methods considered a bad practice?

• It makes the code too fast.

• It complicates the test methods unnecessarily.

• It enhances the readability of the code.

• It reduces the number of test cases.

What is the proposed solution to handle redundant code in test methods?

• Ignore the redundancy.

• Add more test methods.

• Create separate page classes for different functionalities.

• Use more Webdriver APIs.

How does creating separate page classes improve code readability?

• By making the code more complex.

• By increasing the number of lines in the code.

• By organizing code into methods that clearly describe their actions.

• By using more technical jargon.

What should be the role of assertion statements in test methods?

• They should be placed in page classes.

• They should be used to perform actions on the page.

• They should verify the success of the test method.

• They should be avoided entirely.

Why should assertion statements not be included in page classes?

• Because they are not supported by page classes.

• Because they make the code run slower.

• Because page classes should only provide the state of the page.

• Because they are too complex for page classes.

What is the main responsibility of page classes according to the video?

• To perform assertions.

• To provide access to the state of the page and perform actions.

• To increase the complexity of the code.

• To replace test methods entirely.