How to log off the Virtual Machine without any services interruption on the same?

I was working with the VM and always my pulse secure connection was disconnected hence my application was down, So I got the batch file which is logging off the system properly without disconnecting the VPN connection. 

The batch job text is written below:

========================================

@ECHO OFF

C:\Windows\System32\tscon.exe rdp-tcp#0 /dest:console 

C:\Windows\System32\tscon.exe rdp-tcp#1 /dest:console 

C:\Windows\System32\tscon.exe rdp-tcp#2 /dest:console 

C:\Windows\System32\tscon.exe rdp-tcp#3 /dest:console 

C:\Windows\System32\tscon.exe rdp-tcp#4 /dest:console

========================================

And Save the above text as any bat file like "SoftLogOff.bat" and save in the VM system.

While logging off you should double-click on this bat file and then the system will be logged off.

Thank you.

How to restrict second user on Virtual Machine entry while first one is logged on

I find a method that the second user cannot "kick of" the first user.

Do you only want one user access the remote desktop at one time? If so, you can set the Group Policy to limit the number of the connections.

Open the Group Policy Editor, Locate to:
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections

On the right pane, double-click Limite number of connections, click Enable, set the RD Maximus Connections allowed to 1.

In this way, the group policy restricts the second user to log on the remote desktop if someone is using the remote desktop.

Writing text in internet explorer while using element.sendKeys("abc") is very slow.

You can change to the 32-bit version, but in 64 bit IE is required then you can try this solution:

Internet Options -> Security -> Check "Enable Protected Mode" for all zone

Go to Advanced -> Security -> Check "Enable Enhanced Protected Mode"

=> No more snail typing on 64 bit IE (xD)

What is test automation framework and it's basic framework types ?

A test automation framework is a combination of guidelines, coding standards, concepts, practices, processes, project hierarchies, reporting mechanism, test data, to support automation testing. A tester follows these guidelines while automating applications to take advantage of various productive results.

There are many types of test automation frameworks available in the market, and the most popular ones are listed here. Each one of these frameworks has their individual characteristics and features.

Let us now examine some of the popular frameworks and understand their pros, cons, and usability recommendations:

# Keyword-driven framework

In the keyword-driven framework, testers create various keywords and associate different actions or functions with each of these keywords. Function library contains the logic to read the keywords and call and perform the associated actions. Generally, test scenarios are written in excel sheets. The driver script reads the scenario and performs test execution. This is used in situations where the testers who create test scripts have less programming expertise, whereas framework creation is done by automation experts

# Hybrid framework

The hybrid automation framework is created by combining distinct features of two or more frameworks. This enhances the strengths of the different frameworks and mitigates their weaknesses. It is highly robust, flexible, and more maintainable. However, this requires strong technical expertise to design and maintain.

# Behavior-driven development framework

Behavior-driven development (BDD) framework automates validations in an easily readable and understandable format to business analysts, developers, testers, etc. Such frameworks do not

necessarily require the user to be acquainted with any programming language. There are different tools available for BDD like Cucumber, JBehave, and more which work along with other test automation tools. This framework is more suitable for applications using agile methodology and where user stories and early automation are required. It focuses on the behavior of the system rather than the implementation aspect of the system. The traceability between requirements and scripts is maintained throughout, and test scripts are easy to understand for the business users.