Locate, Execute, Expect Design Pattern

Vadan, Andrei-Mihai; Miclea, Liviu

doi:10.1109/aqtr55203.2022.9801987

Cited by 1 publication

(11 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We will discuss testing web applications, user interface testing, and use it to test the API. Before that, we will shortly discuss design patterns and describe in a few words both Page Object Model and Locate, Execute, Expect [16].…”

Section: Design Patterns and Automation Frameworkmentioning

confidence: 99%

“…In this way, we avoid circular dependencies. In Figure 10, we can notice the generic diagram of the LEE design pattern [16]. connect to device for example.…”

Section: Locate Execute Expect Design Patternmentioning

confidence: 99%

“…In this way, we avoid circular dependencies. In Figure 10, we can notice the generic diagram of the LEE design pattern [16]. If it is a must, we can include helper classes, but those are not considered a part of the LEE.…”

Section: Locate Execute Expect Design Patternmentioning

confidence: 99%

Section: Applying the Locate Execute Expect Design Pattern For Ui Tes...mentioning

confidence: 99%

“…We tried to give a basic example in Figure 11. When we click on the 'Login' button, if the credentials we provide in the test work, we should be redirected to another page, and if these credentials are not correct, we should see a pop-up with an error message [16]. We will apply the following test case to test this page: the user will insert 'my_email@email.com' in the 'Username' field, 'mypassword' in the 'Password' field, and will press the 'Login' button.…”

Section: Applying the Locate Execute Expect Design Pattern For Ui Tes...mentioning

confidence: 99%

See 4 more Smart Citations

Software Testing Techniques for Improving the Quality of Smart-Home IoT Systems

Vadan

Miclea

2023

Electronics

Self Cite

View full text Add to dashboard Cite

Software is present in any modern device and is one of the most important components of a new product. IoT systems for smart homes have become more popular in recent years, and testing these systems using advanced methods is very important because it should improve software quality from the beginning of development, resulting in a faster product development overall and a better user experience for the client. In this paper, we describe methods of how to build fast quality assurance software for automation testing in comparison with current trends. Those methods are applicable to teams that are using custom test automation frameworks and working in big projects. The methods have already been applied with success in testing infotainment systems in the automotive industry and our custom-made smart-home IoT system. We will present the system and testing techniques used for testing web interfaces, mobile applications, cross-platform mobile applications, and backend using a new design pattern, called ‘Locate, Execute, Expect’. We compare this new design pattern against Page Object Model and will guide you on how to integrate it in an existing project or how to use it with Gherkin. In conclusion, we will see the main advantages of using this technique and how much faster it is in a real-life scenario, we will learn how it can replace Gherkin, and we will also see the main disadvantages.

show abstract

Section: Design Patterns and Automation Frameworkmentioning

confidence: 99%

“…In this way, we avoid circular dependencies. In Figure 10, we can notice the generic diagram of the LEE design pattern [16]. connect to device for example.…”

Section: Locate Execute Expect Design Patternmentioning

confidence: 99%

Section: Locate Execute Expect Design Patternmentioning

confidence: 99%

Section: Applying the Locate Execute Expect Design Pattern For Ui Tes...mentioning

confidence: 99%

Section: Applying the Locate Execute Expect Design Pattern For Ui Tes...mentioning

confidence: 99%

See 3 more Smart Citations