Telerik Test Studio Limitations

S.No	Description	Category	Solution
1.	Element highlighting will not work.	Development	Set the browser zoom level and system display level to 100% always.
2.	Firefox browser should be configure to open URL in new windows	Development	No solution
3.	Renaming/deleting the elements in Element Explorer will not change in code automatically.	Development	Do not rename/delete the elements used in coded steps.
4.	When recording is started, the elements added will be directly associated to the active test. So, deleting this test will delete all the added elements of the current test.	Development	Open the corresponding test and add the elements or record the steps directly to the active test which are related to current functionality.
5.	When a TTS project is created in Visual Studio and opened in TTS standalone version, the external references will not be available for the tests during runtime	Runtime	Copy the ‘packages’ folder which has the external references and place it inside the project folder where .csproj file exists i.e., inside the TTS project folder.
6.	When test lists are scheduled and changes are made to the same test list later, the latest project files will not be automatically uploaded to storage DB	Runtime	Manually right click on the scheduled test list in the timeline of ‘Results’ section and click on ‘Upload latest project files’ option.
7.	Usage of mouse and keyboard events in the test	Runtime	Works only when the mouse and keyboard focus on the executing browser.  If you are using VM always the screen should be active. If you distribute the tests in different VMs we need those many physical machines.
8.	Launching browsers with custom options	Development	Cannot open browsers in private mode Cannot create our own profiles

Business Continuity/Zero Downtime Testing in Blue Green deployment

As per wiki definition,

“Business continuity encompasses a loosely defined set of planning, preparatory and related activities which are intended to ensure that an organization’s critical business functions will either continue to operate despite serious incidents or disasters that might otherwise have interrupted them, or will be recovered to an operational state within a reasonably short period.”

During deployment

·         Our business should continue with existing production environment and customers should be able to operate and work with our products without any interruption

Once deployment is completed

·         Customer should be able to see the changes in the build and able to operate with our products seamlessly

Business continuity also means that customers should able to operate with our products in case of deployment failures. We should identify the time taken for disaster recovery during hot upgrade deployment in case of deployment failures.

Business continuity can’t be simulated with manual testing alone. In Production, we are not sure how many customers are using our products, what the load on production is and what the customer user cases are. We can automate Business continuity tests by continuously running the tests before and during upgrade deployment. We should make sure that none of the automated tests should fail during upgrade deployment because of deployment issues. We are calling this as Business Continuity/zero downtime testing.