Loading via script tag might give issues reloading script, as it makes the script part of DOM, but does allow debugging via dev console.
Enabling a package override replaces the package with a browser implementation.
This generally improves speed, at the cost of test accuracy.
Past Plugins
{{pastPluginUrl}}
{ev.stopPropagation(); deletePastPlugin(pastPluginUrl)}">
X
Errors in Plugin
{{Plugin.currentPluginError}}Your plugin is loaded
You can now use testing methods available on the webapp.The information and warnings the user will see when installing the app can be viewed below.
Last updated: {{Plugin.lastLoadTime}}
{{Plugin.currentPlugin.name}}
{{Plugin.currentPlugin.description}}
Version
{{Plugin.currentPlugin.version}}
Repository URL
Script URL
Warnings
These are the warnings a user will see when they attempt to install this plugin
security
{{warning.first}}
{{warning.second}}
Load a plugin before doing testing.
(Optional)
{{req.title}}
{{req.description}}
{{req.code}}
{{parameter.name}}
{{parameter.description}}
Results
No test done yet
{{Testing.lastResult}}
{{Testing.lastResultError}}
Load a plugin before doing integration testing.
Errors in Plugin
Its best to fix errors before doing any integration testing
Integration testing allows you to upload your loaded plugin onto your phone, and get logs below to find any exceptions in actual usage.
Last Injected: {{Integration.lastInjectTime}}
Click Inject Plugin again to update to last version.
Click Inject Plugin again to update to last version.
Plugin is not yet injected. Click "Inject Plugin" to load the plugin on your phone.
[{{line.type}}]
{{line.log}}
{{exchange.response.status}}
{{exchange.request.method}}
{{exchange.request.url}}
Request Headers
{{header}}
{{headerValue}}
Response
{{header}}
{{headerValue}}
{{exchange.response.body}}