development
/
webtester
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Test your websites with this simple GUI based scripted webtester. Generate simple testscripts directly from surfng on the webpage, enhance them with your commands, with variables, loops, checks, … and finally run automated web tests.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
36 Commits
1 Branch
1 Tag
17 MiB
 
 
 
 
 
 
Tag: Branch: Tree: bf6b4764db
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'bf6b4764db'
${ noResults }
Go to file
Marc Wäckerlin bf6b4764db
better doxygen support 		9 years ago
debian reprepo requires a section 9 years ago
doc better doxygen support 9 years ago
docker new build system 9 years ago
scripts better doxygen support 9 years ago
src massively improved build system 9 years ago
AUTHORS ready to build debian packages 9 years ago
COPYING ready to build debian packages 9 years ago
ChangeLog better doxygen support 9 years ago
INSTALL ready to build debian packages 9 years ago
NEWS ready to build debian packages 9 years ago
README massively improved build system 9 years ago
ax_check_qt.m4 massively improved build system 9 years ago
ax_cxx_compile_stdcxx_11.m4 new build system 9 years ago
ax_init_standard_project.m4 added doxygen-webtester.sed do generate doxygen from webtester files 9 years ago
bootstrap.sh better doxygen support 9 years ago
configure.ac added doxygen-webtester.sed do generate doxygen from webtester files 9 years ago
makefile.am added doxygen-webtester.sed do generate doxygen from webtester files 9 years ago

README 

Test Your Web Application: GUI Web Testing Environment + Script Runner

Webtester consists of two binaries: webtester to interactively create your web application tests and webrunner to run your test scripts.

There is a test GUI including browser to record user input while he surfs on the web and a test runner to run (recorded) test scripts. The tests can be integrated e.g. in a jenkins build job. It has been tested on Wordpress, Dokuwiki and Joomla pages. Joomla is difficult due to Javascript-Moo-Tools pollution. There's some specific support, that may help a bit, but to test Joomla sites, you need a lot of experience. Concluson: Avoid Joomla.

Sample Script to search my old homepage on Google, klick on the link, there click on tab «Computer» and check the title for the text «Marcs Computerblog»:

load https://google.com
expect load
setvalue input[name="q"] -> 'Marc Wäckerlin';
click input[name="btnG"]
expect load
click a[href^="/url?q=https://marc.waeckerlin.org/&"]
expect load https://marc.waeckerlin.org/doku.php
click a[href="/computer/index"]
expect load https://marc.waeckerlin.org/computer/index
exists h1.sectionedit1 -> Marcs Computerblog