Methods for improved web application testing using remote headless browsers and devices thereof

1. A method for web application testing, the method implemented by one or more runner servers and comprising:

executing a test of a web application with a headless browser activated in response to a request to schedule the web application test received from a dashboard server, wherein the web application test comprises a plurality of test actions;

sending an input request comprising at least a hint and a session identifier to the dashboard server in response to a user input trigger associated with one of the test actions during the execution of the web application test by the headless browser;

executing the associated one of the test actions with the headless browser and using input data received from the dashboard server in response to the input request; and

recording during the execution of the web application test, and outputting to the dashboard server when the web application test is complete, one or more web pages associated with the web application and analysis results.

2. The method of claim 1 , wherein the hint is defined in the one of the test actions and corresponds with an aspect of an input element of a web page of the web application and the input request further comprises an input type defined in the one of the test actions.

3. The method of claim 1 , further comprising receiving the session identifier from the dashboard server in response to a chat group request sent to the dashboard server based on test configuration data received with the request to schedule the web application test.

4. The method of claim 1 , further comprising providing the input data to the headless browser via a shared working directory in a local memory, wherein the input data is obtained from a user device via an input panel provided to the user device and associated with the session identifier.

5. The method of claim 1 , further comprising sending a progress request to the dashboard server upon encountering a progress trigger during the execution of the web application test, wherein the progress request comprises the session identifier and an indication of another one of the test actions associated with the progress trigger.

6. The method of claim 1 , further comprising sanitizing at least one of the web pages to remove at least the input data prior to at least one of recording the one of the web pages or outputting the one of the web pages to the dashboard server, wherein the one of the web pages is associated with the one of the test actions.

7. A runner server, comprising memory comprising programmed instructions stored thereon and one or more processors configured to execute the stored programmed instructions to:

execute a test of a web application with a headless browser activated in response to a request to schedule the web application test received from a dashboard server, wherein the web application test comprises a plurality of test actions;

send an input request comprising at least a hint and a session identifier to the dashboard server in response to a user input trigger associated with one of the test actions during the execution of the web application test by the headless browser;

execute the associated one of the test actions with the headless browser and using input data received from the dashboard server in response to the input request; and

record during the execution of the web application test, and output to the dashboard server when the web application test is complete, one or more web pages associated with the web application and analysis results.

8. The runner server of claim 7 , wherein the hint is defined in the one of the test actions and corresponds with an aspect of an input element of a web page of the web application and the input request further comprises an input type defined in the one of the test actions.

9. The runner server of claim 7 , wherein the one or more processors are further configured to execute the stored programmed instructions to receive the session identifier from the dashboard server in response to a chat group request sent to the dashboard server based on test configuration data received with the request to schedule the web application test.

10. The runner server of claim 7 , wherein the one or more processors are further configured to execute the stored programmed instructions to provide the input data to the headless browser via a shared working directory in a local memory, wherein the input data is obtained from a user device via an input panel provided to the user device and associated with the session identifier.

11. The runner server of claim 7 , wherein the one or more processors are further configured to execute the stored programmed instructions to send a progress request to the dashboard server upon encountering a progress trigger during the execution of the web application test, wherein the progress request comprises the session identifier and an indication of another one of the test actions associated with the progress trigger.

12. The runner server of claim 7 , wherein the one or more processors are further configured to execute the stored programmed instructions to sanitize at least one of the web pages to remove at least the input data prior to at least one of recording the one of the web pages or outputting the one of the web pages to the dashboard server, wherein the one of the web pages is associated with the one of the test actions.

13. A non-transitory computer readable medium having stored thereon instructions for web application testing comprising executable code which when executed by one or more processors, causes the one or more processors to:

execute a test of a web application with a headless browser activated in response to a request to schedule the web application test received from a dashboard server, wherein the web application test comprises a plurality of test actions;

send an input request comprising at least a hint and a session identifier to the dashboard server in response to a user input trigger associated with one of the test actions during the execution of the web application test by the headless browser;

execute the associated one of the test actions with the headless browser and using input data received from the dashboard server in response to the input request; and

record during the execution of the web application test, and output to the dashboard server when the web application test is complete, one or more web pages associated with the web application and analysis results.

14. The non-transitory computer readable medium of claim 13 , wherein the hint is defined in the one of the test actions and corresponds with an aspect of an input element of a web page of the web application and the input request further comprises an input type defined in the one of the test actions.

15. The non-transitory computer readable medium of claim 13 , wherein the executable code when executed by the one or more processors further causes the one or more processors to receive the session identifier from the dashboard server in response to a chat group request sent to the dashboard server based on test configuration data received with the request to schedule the web application test.

16. The non-transitory computer readable medium of claim 13 , wherein the executable code when executed by the one or more processors further causes the one or more processors to provide the input data to the headless browser via a shared working directory in a local memory, wherein the input data is obtained from a user device via an input panel provided to the user device and associated with the session identifier.

17. The non-transitory computer readable medium of claim 13 , wherein the executable code when executed by the one or more processors further causes the one or more processors to sending a progress request to the dashboard server upon encountering a progress trigger during the execution of the web application test, wherein the progress request comprises the session identifier and an indication of another one of the test actions associated with the progress trigger.

18. The non-transitory computer readable medium of claim 13 , wherein the executable code when executed by the one or more processors further causes the one or more processors to sanitize at least one of the web pages to remove at least the input data prior to at least one of recording the one of the web pages or outputting the one of the web pages to the dashboard server, wherein the one of the web pages is associated with the one of the test actions.