Versions Compared

Old Version 29

changes.mady.by.user Shruti Agrawal

Saved on

compared with

New Version 30

changes.mady.by.user Shruti Agrawal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The Scheduler execution is not working on Safari browser due to failure of Webdriver object creation.

  • When you create a new connection using the Salesforce application and try to import objects, you will see additional object entries under the Import Object section.

  • Not be able to load the SFDC project after an upgrade: If you are not able to load the SFDC project after an upgrade to Qualitia’s latest version, you need to delete the Workspace folder. You can find the workspace folder on the below path: C:\Users\user1\AppData\Local\Qualitia Automation Studio - Client\workspace.

  • Newly added objects are not visible on Import model: If you are not able to find a newly added object on the import model, while creating an object create it as mandatory and save. Once the object is saved, make it non-mandatory, as only mandatory fields are visible on the Import modal. This will make the object visible and ready to be used.

  • Getting error "Early EOF" while project setup after replacing the server workspace: You might get this error while project setup if the credentials through which the VM was logged-in is different from which the Web Services were started. To avoid getting this error you have to make sure that the same log in credential is used for VM as well as web services. To fix this error, refer https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857452383/Project+Creation#%F0%9F%94%A7-Got-Trouble%3F-Let%E2%80%99s-Fix!

  • Error while fetching objects for connection: If you are getting the error message Error while fetching objects for connection, while importing the objects, make sure to enable the Client credential flow on the Connected App.
    Note: You can also connect using OAuth Client Credential to avoid such errors.

  • Mobile test case execution is failing on ADO: To execute mobile test case successfully on ADO, you need to provide all the mobile capabilities manually. Please refer https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857454550/Azure+DevOps+Integration#%F0%9F%94%A7-Got-a-problem%3F-Let%E2%80%99s-fix! for detailed steps on how to add mobile capabalitiescapabilities.

  • Schedular execution is not working when there is more than 1 test case giving error "ALL TC ITERATIONS MARKED FALSE".

Qualitia Automation Studio - 9.0

...