Old test db has been deprecated and will no longer work.
Switch test over to use dockerized or sqlite database.

Update the namespace to use Cognizant

Add module similar to the Selenium module
Include:
BaseTest
TestObject
DriverManger
DriverFactory
BasePageModel
Config

Override values can be accidently put into the run config context, which means are not removed when we ClearOverrides.

Repo code
In the following example the GetBrowser test will fail because it find Webkit when it expects Chrome:

    [TestClass]
    [ExcludeFromCodeCoverage]
    [DoNotParallelize]
    [TestCategory(TestCategories.Playwright)]
    public class PlaywrightConfigTests
    {
        /// <summary>
        /// Clear all configuration overrides
        /// </summary>
        [TestInitialize]
        public void Setup()
        {
            Config.ClearOverrides();
        }

        /// <summary>
        /// Get expected WebBase configuration
        /// </summary>
        [TestMethod]
        public void GetBrowser()
        {
            Assert.AreEqual("Chrome", PlaywrightConfig.GetBrowserName());
        }

        [DataTestMethod]
        [DataRow("Chrome")]
        [DataRow("Chromium")]
        [DataRow("Firefox")]
        [DataRow("Edge")]
        [DataRow("Webkit")]
        public void ConfigBrowserName(string browserName)
        {
            Config.AddTestSettingValue("Browser", browserName, ConfigSection.PlaywrightMaqs);
            Assert.AreEqual(browserName, PlaywrightConfig.GetBrowserName());
        }
}

Change nutget reference of Troy's repo to this one:
https://github.com/dequelabs/axe-core-nuget

The NuGet package will be deprecated and https://www.nuget.org/packages/Deque.AxeCore.Selenium/ will be set as the alternate package

• The new Deque project will support both Selenium and Playwright
• A new project (https://github.com/microsoft/html-reporter-for-axe-core-dotnet) will be used for creating HTML reports. This should provide a much better user experience than the admittedly primitive reporting currently included in Selenium.Axe

If we update to System.Drawing.Common to 6.0.0, we get the following error on the build server:
System.TypeInitializationException: The type initializer for 'Gdip' threw an exception. ---> System.PlatformNotSupportedException: System.Drawing.Common is not supported on non-Windows platforms.

See https://aka.ms/systemdrawingnonwindows for more information.

We likely need to move off System.Drawing.Common.

The MAQS acronym should change
from:
"Magenic's automation quick start"
to:
"Modular automation quick start"

From https://learn.microsoft.com/en-us/sql/connect/ado-net/introduction-microsoft-data-sqlclient-namespace?view=sql-server-ver16

The Microsoft.Data.SqlClient namespace is essentially a new version of the System.Data.SqlClient namespace. Microsoft.Data.SqlClient generally maintains the same API and backwards compatibility with System.Data.SqlClient

This would give us access to new and helpful functionalities like setting the Command Timeout directly from the Connection Strings. MAQS does currently support setting the Command Timeout but this needs to be set for every Query method call. This would help us support long running queries from specific databases.

Update in: https://github.com/CognizantOpenSource/maqs-dotnet/blob/main/Framework/BaseDatabaseTest/Providers/SQLServerProvider.cs

Add a Playwright base step to gherkin extension

Magenic name is going away so switch config to global

Code coverage numbers are incorrect in SonarCloud

When you override the base web driver in a class derived from BaseSeleniumPageModel or BaseAppiumPageModel it is not respected by any of the lazy elements.

Existing implementation to workaround the issue.

// Take care of null and missing values encountered during deserialization
var settings = new JsonSerializerSettings
{
	NullValueHandling = NullValueHandling.Ignore,
	MissingMemberHandling = MissingMemberHandling.Ignore
};
var jsonString = responseMessage.Content.ReadAsStringAsync().Result;

return JsonConvert.DeserializeObject<MyObject>(jsonString, settings);

The existing WebServiceUtils does not have the ability to add JsonSerializerSettings to assist with different object mappings coming back

Get packages and pipelines ready to push to nuget.org

A version 3 of MSTest and its related packages (MSTest.Framework and MSTest.TestAdapter) have been released. MAQS is currently in use at RSM for test automation, and they would like to take advantage of features in version 3.

I tried just updating the packages in a branch off of main, and it looks like there already are some breaking changes to Assert.AreNotEqual and Assert.AreEqual when comparing two Object instances that folks will have to be aware of when upgrading.

Is it possible for this to make it into the next release? Are there any other obstacles to upgrading MSTest to v3?

Thanks,

Brannen

When MAQS logging is set to onfail, it will create an extra log file for each passing test.
These files provide no value and only fill up the folder.

The Magenic test site and services (https://magenicautomation.azurewebsites.net) will be deprecated soon.
We will need to host other test resources for MAQS going forward.

I am running into an issue where SeleniumMaqs::Browser is not being read properly from appsettings.json. The error is only happening in JetBrains Rider, but as this is a widely used C# IDE this seems like something worth fixing.

Steps to reproduce:

1. Using the MAQS Templates generate a Composite project
2. Change SeleniumMaqs::Browser from Chrome to Edge
3. Open solution in VisualStudio or VSCode
4. Run test SeleniumTests::EnterValidCredentialsTest
   a. Expected: Test runs in Edge
   b. Actual: Test run in Edge
5. Open solution in JetBrains Rider
6. Run test SeleniumTests::EnterValidCredentialsTest
   a. Expected: Test runs in Edge
   b. Actual: Test run in Chrome

This is only a selenium issue. If I change PlaywrightMaqs::Browser from Chrome to Edge and run PlaywrightTestsVSUnit::EnterValidCredentialsTest then, as expected, the test runs in Edge.

EDIT:

This ended up being a settings issue. There was a .runsettings file from a different project overriding the default configs.

I tried following directions in the documentation to install the templates and get this error. All I did was install the latest .NET SDK and then run the command in the MAQS 9.0.0 documentation. Did I do something wrong or am I missing something?

Edit:

I was able to get this to work by adding the version explicitly.

dotnet new --install CognizantSoftvision.Maqs.Templates::9.0.0

This still seems like an issue. Either in configuration or documentation.

Appium 2 has been released for a while now, but there has been no update to the released version in MAQS. Is an update being worked on to the released Appium 2 version?

Use marketing provided icons and images

Hi Team,
Due to Chrome browser changes, unable to execute test cases for Chrome V115+ in local.

Exception -> Your web driver may be out of date or unsupported. ---> System.Net.WebException: The remote server returned an error: (404) Not found.

Might require some changes in the framework at

1.ChromeDriverServices (new ChromeDriverDownloadUrl for driver download ->
https://googlechromelabs.github.io/chrome-for-testing/)

2. Additional changes to incorporate the usage of Chrome.exe for testing

Kindly help.

Thanks,
Dbedutta