Test Automation and EasyRepro: 03 – Extending the EasyRepro Framework

by Contributed | Jan 11, 2021 | Technology

This article is contributed. See the original author and article here.

The following is the third on a series of articles by @Ali Youssefi that we will be cross-posting into this Test Community Blog. These articles were first published by Ali in the Dynamics community but since the topic is very related with Testing it makes sense to publish here as well.

If you didn’t get a chance to catch the first one of the series, please have a look here: 

• Test Automation and EasyRepro: 01 – Overview and Getting Started


• Test Automation and EasyRepro: 02 – Designing and Debugging Unit Tests

Otherwise, please read ahead!

Summary

EasyRepro is an open source framework built upon Selenium allowing automated UI tests to be performed on a specific Dynamics 365 organization. This article will focus on reviewing how EasyRepro works with the Document Object Model otherwise known as the DOM. This will help us understand how we can extend the EasyRepro code for use with custom objects or areas of the platform not included in the framework at this time. We will wrap with a brief look at XPath and referencing elements from the DOM.

Getting Started

If you haven’t already, check out the first article which covers getting familiar with EasyRepro and working with the source code locally. It covers cloning from GitHub to Azure DevOps then from Azure DevOps Git repository to a development machine. and reviews setting up dependencies and test settings to run a simple test. The second article goes into common actions performed by users when interacting with Dynamics 365 and the correlating EasyRepro commands. It wraps with covering common troubleshooting and debugging scenarios.

The EasyRepro framework contains an abundance of commands that should suit most of your needs. However you’ll find that at times either these commands will need to be modified per your customizations or you may need to create your own custom commands for reuse among tests. 

Some example scenarios for modifying or creating custom commands may include:

1. 
   

   Using an ADFS Redirect Login

   
   


2. 
   

   Working with custom components and resources

   
   


3. 
   

   Working with strongly typed entity attributes

   
   


4. 
   

   Including navigation and functionality not present natively in the framework

   
   

These scenarios require an understanding of how EasyRepro interacts with Selenium to simulate user actions in a browser. This article will focus on a typical use case for extension: the Login process. We will describe common Selenium functionality and how to reference elements on the Document Object Model in a way to increase maintainability.

Sample Scenarios for Extending

Working with the Browser Driver

As we discussed earlier, your organization’s login process may have a sign on page that a user will get redirected to once they input their username. This is where we begin our journey into extending the framework and utilizing Selenium.

Typical Single Sign On Page:

Custom method for a Single Sign On Page:

The image above shows a method designed to search through a sign in page DOM for input fields for credentials and submission. You will notice that we are working with the browser driver natively (args.Driver) and using methods not found in the sample EasyRepro unit tests. These include FindElement which is part of Selenium and WaitForPageToLoad which is part of EasyRepro’s extension of Selenium. I’ll touch on these at a high level now.

FindElement

FindElement is part of the Selenium.WebDriver assembly and is used to find an element in the DOM. I’ll cover how to search through the DOM in the next section Extending and Working with XPath but I wanted to take this time to show how we will begin extending unit tests using Selenium natively.

The  method returns an IWebElement object that represents the element you want to work with. For instance if you want to work with the username textbox you can use FindElement to locate and return the username textbox. Once returned the framework can interact with it and perform actions such as input text or click.

Reference:

https://www.toolsqa.com/selenium-webdriver/c-sharp/findelement-and-findelements-commands-in-c/

WaitForPageToLoad

WaitForPageToLoad is part of the EasyRepro framework as a Selenium extension. This is key to point out that we are leveraging both EasyRepro and Selenium natively to achieve our desired result to login. This method waits a specific amount of time and checks for the document ready state. The time interval used to check can be adjusted if needed.

SendKeys and Clear

SendKeys is used to send keystrokes to an element on the page. This can be a complete string such as an email or a single keypress. This can be used to send the username and password to your sign in page. It also can be used to send the Enter or Tab keypress to move to the next field or submit.

Clear as it sounds is used to remove any sort of input that may already exist in an element. This is useful if your sign in page attempts to automatically input credentials.

Both of these methods are part of the IWebElement shown above. Other useful properties of IWebElement include Text, Selected and GetAttribute.

Understanding how to extend element references

Considerations need to be made when designing unit tests to help reduce the maintenance work needed if something changes. For instance when referencing custom HTML web resources or even the ADFS Redirect from above, think how a change to an element in the DOM could propagate across some of all of your unit tests. One way to control maintenance is to centralize commonly used references into proxy objects that can hide the underlying mechanics from the test designer. This is exactly how the EasyRepro framework handles references and when extending can leverage the same approach. In this section we will cover the files used by the framework to reference DOM elements and show how to extend them to include references to our custom login page.

The App Element Reference File

The Microsoft.Dynamics365.UIAutomation.Api.UCI project uses the ElementReference.cs file as well as another file called AppElementReference.cs. The ElementReference file looks to have been brought over from the classic interface. What’s unique about each is how they reference elements in the DOM which I’ll cover in the next section. For now let’s focus on reviewing the AppElementReference.cs file which is located in the DTO folder of the Microsoft.Dynamics365.UIAutomation.Api.UCI project.

Inside of the AppElementReference file are two objects used by EasyRepro to represent and locate elements: The AppReference and AppElements classes.

The AppReference class

The AppReference class includes sub classes that represent the objects used by EasyRepro, specifically the WebClient object, to connect to DOM elements. This allows the framework to standardize how the search for a particular container or element is performed. Centralizing the reference to the DOM elements will allow the test designer to focus on writing commands against common objects and not specifying the precise location of an element in the DOM.

The AppElement class

The AppElement class is a comma delimited key value pair consisting of the reference object property as a key and the XPath command as the value. The key represents the property name in the class object inside of AppReference while the value is the XPath location of the element in the DOM.

I highly suggest reviewing the AppElement class when extending EasyRepro as it shows recommended ways to locate and reference elements on the DOM. In the next section we will discuss the different ways you can locate elements including XPath.

Referencing elements in the Document Object Model

References to objects generally fall into four patterns:

1. 
   

   Resolving via Control Name

   
   


2. 
   

   Resolving via XPath

   
   


3. 
   

   Resolving by Element ID

   
   


4. 
   

   Resolving by CSS Class

   
   

In this article we will focus on XPath which is what is primarily used by the EasyRepro framework for the Dynamics 365 platform. However its key to understand each of the approaches for referencing as they can be used for customizations such as web resources, custom controls, etc.

Resolve with Control Name

This will search the DOM for elements with a specific name which is an attribute on the element node. This is not used by EasyRepro to my knowledge. Elements can be found by their name by using By.TagName with the FindElement method.

Resolve with Element ID

This will attempt to find an element by its unique identifier. For instance a textbox on the login form maybe identified as ‘txtUserName’. Assuming this element ID is unique we could search for this particular element by an ID and return an IWebElement representation. An example from the Microsoft.Dynamics365.UIAutomation.Api.UCI project is shown below showing usage with the timeline control.

Definition:

Usage by WebClient:

Elements can be found by their ID by using By.Id with the FindElement method. 

Resolve with CSS Class

This allows the ability to search by the CSS class defined on the element. Be aware that this can return multiple elements due to the nature of CSS class. There is no usage of this in EasyRepro but again this could be helpful for customizations. Elements can be found by their CSS class name by using By.Class with the FindElement method.

Resolve with XPath

XPath allows us to work quickly and efficiently to search for a known element or path within the DOM. Key functions include the contains method which allow to search node attributes or values. For instance when you review the DOM of a form you’ll notice attributes such as data-id or static text housed within a span element. Coupling this attribute with the html tag can result in a surprisingly accurate way to locate an element. I suggest leveraging the current element class as well as this link from W3 Schools that goes into the schema of XPath.

Going back to an earlier section let’s review how XPath along with the AppElementReference.cs file can help standardize element location.

Using XPath in the ADFS Redirect Login Method

Going back to our original example for the ADFS login method below you’ll see an example of referencing the DOM elements using XPath directly with the Selenium objects driver and By.XPath. Consider the below two images:

Without a static representation of XPath:

Using static classes to represent XPath queries:

Both of these methods work and perform exactly the same. However the second method provides increased supportability if and when the login page goes through changes. For instance consider if the id of the textbox to input your username changes from txtUserName to txtLoginId. Also what if this txtUserName XPath query is propagated across hundreds or more unit tests?

Creating custom reference objects

Let’s put what we have learned to use by creating a reference to our custom login page. Start by adding a class to the AppReference object and title it AdfsLogin. Inside this class declare string properties that will be used as input for your organization’s login page. Typical inputs include username, password and a submit button. Here is an example:

NOTE: While this document demonstrates how to add to the AppElementReference.cs file I would suggest extending this outside of the core files as customizations will have to be merged with any updates from the framework.

Once the static class we want to use in our unit tests has been created we now need to add the XPath references to the AppElement class. Below is an image showing the key value pair discussed in the AppElement section above. The key correlates to the string value of the AdfsLogin class while the value is the XPath directive for our elements.

As shown in the image for Login_UserId we are searching the DOM for an input element with the id attribute of ‘txtUserName’. XPath can be used to search for any attribute on the DOM element and can return a single value or multiple depending on what you’re searching for.

Next Steps

Custom Components and Web Resources

PowerApps Control Framework controls and web resources are customizations that represent great options to learn and extend the EasyRepro framework. Try locating the container for the PCF controls and HTML web resources and work towards creating custom objects representing the elements for each as described above.

Conclusion

In this article we discussed reasons why we will may need to extend the EasyRepro framework and some techniques in doing so. We explored working with Selenium objects and creating references to help us when creating unit tests. Finally we put this in an example for working with a ADFS Redirect page on login.

Thank you again for reading! Please let me know in the comments how your journey is going!

Upcoming Mid-Day Café Webcast Schedule

by Contributed | Jan 11, 2021 | Technology

This article is contributed. See the original author and article here.

The following is the tentative Mid-Day Café Schedule for Monday Webcast taking place at 12 noon EST/9 am Pacific. Follow the HLS Blog for individual Posts with further details, links/calendar invites to the webcasts, as well as any adjustments on topics and dates. We will provide individual posts for each event starting tomorrow 1/12/2021.

We look forward to you joining us live, as well as watching/sharing the posted recordings and resources. If you have questions/comments/requests/shout-outs be sure to drop us a line in our mailbag. We love hearing from you all!

Tentative Schedule:

• January 18 –   No Mid-Day, Martin Luther King Day


• January 25 –   No Mid-Day, HLS H2 Internal Kickoff


• February 1 –   Nikita Pitliya and Gregory Lisiak, COVID Vaccine Health Bot


• February 8 –   Andres Santamaria, Epic FHIR API Integration


• February 22 – Bill Baer, Microsoft Search


• March 1 –       Dan Holme, Community/Yammer


• March 8 –       Mark Kashman, Microsoft Lists


• March 15 –    Karuana Gatimu, Teams Adoption and Governance

Resources:

• HLS Blog 


• Mid-Day Café Mailbag 

Thanks for visiting – Michael Gannotti   LinkedIn | Twitter

Michael Gannotti

Inside look at the new Surface Hub 2S 85

by Contributed | Jan 11, 2021 | Technology

This article is contributed. See the original author and article here.

If you want to see the largest Surface device ever made, check out our latest episode of Microsoft Mechanics for a tour of the most immersive in-person and virtual meeting experience available today. And I can attest. In these last few months, I’ve had the good fortune to use Surface Hub 2S 85” in meetings with customers and PMs across Microsoft and experience a newly discovered presence of working together in one place.

Latest OS and apps

Surface Hub 85” runs the new Windows 10 Team 2020 Update operating system and comes pre-loaded with your favorite Office and Microsoft 365 apps. Now you can join meetings instantly from Surface Hub or even using your own personal device with “proximity join.” And once the meeting is ended all user data is wiped from the device ready for the next session.

Setting up Hub 2S 85”

Compared to the original 84” Surface Hub, the new Hub 2S 85” is significantly easier to install and setup with more optional certified accessories to choose from. For ease of use, I’m a big fan of the Steelcase Roam floating wall mount – no specialized equipment required! And if you’d rather use it in multiple spaces, the Steelcase Roam Mobile Stand makes transportation of the device into your room easier.

Packaging of the Surface Hub 2s 85” has been completely redesigned with a wheeled pallet that fits into most modern elevators. Be sure to check out our newly released Unboxing and Setup video and companion readiness documentation on Microsoft Docs.

Deploying and managing Surface Hub

IT admins can take advantage of extended device policies for more granular management with Microsoft Endpoint Manager or your preferred MDM solution. Device management improvements include Azure Active Directory single sign-on, conditional access, more flexible administrator role support, and secure passwordless sign-on. And with the Microsoft store, device admins can choose from an expanding ecosystem of certified apps for Surface Hub.

Security

All Surface Hubs running Windows 10 Team 2020 Update incorporate silicon level protections with a discrete TPM 2.0 chip and secure boot. The result is a fully locked-down operating system that only allows certified drivers and Windows store apps to run. The OS blocks all drivers except validated inbox drivers and uses system-level policies based on AppLocker to prevent malicious code execution.

Run Windows 10 Pro and Enterprise

Ever since we released surface Hub, customers have sometimes asked me if they could install the standard Windows 10 OS and use Hub just like any PC. Well now you can on both Hub 2S 50″ and the 85″ model.  Installing Windows 10 Pro or Enterprise gives you the flexibility to customize Surface Hub with your favorite win32 apps. And exclusive to Windows 10 Pro and Enterprise, you can use the Surface Hub 2 Fingerprint Reader for secure multifactor biometric sign-on with Windows Hello.

Learn more

For availability and more information, go to Surface.com.

Surface Pro 7+ brings next level performance and versatility to the enterprise

by Contributed | Jan 11, 2021 | Technology

This article is contributed. See the original author and article here.

Surface Pro 7+ for Business, the latest generation of the class defining Surface 2-in-1 delivers next level performance and versatility to commercial enterprises and educational institutions.

Key differences with Surface Pro 7+ for Business:

• Removable SSD with options of up to 1 terabyte of storage making it easier for organizations to retain and protect sensitive information.


• Optional LTE Advanced so you can stay connected and receive the latest updates wherever you go.


• Up to 15 hours of battery life (4.5 hours more than Pro 7) plus fast charging that restores battery levels to 80 percent in about an hour.

As a program manager in the commercial engineering group, I’ve been fortunate to learn directly from customers about what matters most when it comes to choosing the best devices for their company and employees.  Of course, what stands out as top of mind for almost everyone is ease of device deployment and manageability along with built in, chip to cloud security. So it’s with that lens that I’d like to do a quick tour of our newest Surface 2-in-1, beginning with the different ways you can use the device.

More control with cloud-first device deployment and management

Surface Pro 7+ offers some of the most flexible device management options. Starting with device procurement, before devices are shipped using the Windows Autopilot service Surface Pro 7+ can be placed under management and personalized with required apps and policies, enabling factory direct delivery to your users.

Defense in depth with protection from Microsoft

Every layer is maintained by Microsoft, from the hardened firmware that is adopted from a Microsoft open-source UEFI, to the operating system, through to cloud management. Once devices are up and running, using the Device Firmware Configuration Interface (DFCI), hardware capabilities like built-in cameras, microphones, speakers and radios can be individually disabled at the firmware level using cloud-based policy settings from Intune and Microsoft Endpoint Manager.

Optional LTE Advanced

Of course, a big differentiator for Surface Pro 7+ is the optional LTE Advanced connectivity. Surface Pro 7+ with LTE Advanced is available with the fan-less Core i5 configuration and works with both eSIM and physical nano SIM. Instead of handing out physical SIM cards to your mobile workforce, you can centrally manage calling and network data using eSIM based LTE services.

We’ve now expanded our eSIM ecosystem, giving you more options for geographical coverage. In fact, the eSIM profile in Surface Pro 7+ unlocks access to more mobile operators and services in over 180 countries. Additionally, LTE Advanced can ensure reliable network and internet connections and works in tandem with built-in Wi-Fi 6 capabilities, to avoid dropped video calls and to provide resiliency when Wi-Fi connections aren’t reliable or available. And because Surface Pro 7+ with LTE Advanced is typically always connected, devices can receive updates as soon as they become available.

Inside Surface Pro 7+

Surface Pro 7+ uses the latest 11^th gen Intel Core processors more than doubling the performance of the previous generation. And it’s 3.5 times faster than Surface Pro with LTE Advanced from 2017. 

Intel 11^th Gen “Tiger Lake” processors

With options for Core i3, i5, and i7 processors, Surface Pro 7+ is the first Surface Pro device to offer up to 32 gigabytes of RAM and 1 Terabyte of storage. Of course, Surface Pro 7+ supports Wi-Fi 6 and Bluetooth 5.0. This, combined with the optional LTE Advanced, gives you enhanced connectivity.

Design innovations help boost battery run time

The new thermal design is the most efficient and compact to date. It uses graphite heat spreading, heat pipes and carbon composite materials along with larger vents.  Core i7 is designed to minimize fan speed and noise to only the most intensive workloads, while the Core i3 and i5 models are silent and fan-less. We also worked on freeing up internal space by incorporating the same breakthrough technology of Surface Pro X, reducing the thickness of the display. The resulting space advantage went toward increasing the size of the battery. Surface Pro 7+ has the largest battery to date in a Surface Pro with a 50.4-watt hour capacity for improved all-day battery life.

Removable SSD

Surface Pro 7+ provides a removable storage solution that helps commercial organizations comply with specific data retention standards. It also facilitates servicing and repair in the unlikely event of an SSD failure. Enterprise customers no longer need to ship devices back to Microsoft, leaving employees with loaner devices for days.

Retaining proprietary information is made easy with the ability to replace the SSD on-site. Company assets remain in the company with this new option for same unit repair. These offerings include the rSSD and the SSD Door. Purchase of replacement SSDs will be available to commercial customers through authorized resellers beginning with US distribution.

Compatible accessories

Because it uses the same proven design as Pro 7, companies can leverage their investment in compatible Surface Pro accessories like type covers, cases, pens and certified third-party accessories.

Virtual meetings come to life

Support for 1080p Full HD video combined with the dual Studio Microphone array for accurate audio capture makes Surface Pro 7+ ideal for video calls. And, its stereo speakers provide rich sound reproduction using Dolby Atmos®. Capture whiteboard meeting notes and scan documents with the rear-facing 8.0 megapixel HD camera. The high-resolution 12.3” PixelSense™ Display touchscreen features ambient light sensing that automatically adjusts to lighting conditions.

Connect dual 4K monitors

You can easily connect additional monitors using the USB-C port or via the optional Surface Dock 2. The USB ports or Surface Connect can support two external displays with up to 4k resolution, at 60 hertz while working simultaneously with the built-in display, which is great to dock at an office or home office workstation.

Sustainable packaging

Then during shipping, for commercial and bulk shipments, Surface Pro 7+ devices are placed in 23% lighter packaging using device folios. This also makes them easier to distribute broadly, while minimizing waste by using 99% natural fiber-based material, of which 64% is post-consumer recycled materials. And of course, this also makes the devices easier to unpack.

Surface for Business unlocks more value

In summary, Surface Pro 7+ enables businesses and organizations to save time and money with streamlined deployment, modern device management, and built-in, cloud-powered security along with connected experiences from Surface and Microsoft 365. Confidently invest in Surface for today and the future with accessories that are compatible across generations.

To learn more, get a tour from the latest episode of Microsoft Mechanics:

Learn more

For availability and to learn more, see Surface.com.