Bug 19883

Summary: Add a selenium script to hit all the pages
Product: Koha Reporter: Jonathan Druart <jonathan.druart>
Component: Test SuiteAssignee: Jonathan Druart <jonathan.druart>
Status: In Discussion --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: m.de.rooy, mtj, tomascohen
Version: unspecified   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Bug Depends on:    
Bug Blocks: 19384    
Attachments: Bug 19883: Add a selenium script to hit all the pages

Description Jonathan Druart 2017-12-27 13:01:19 UTC

    
Comment 1 Jonathan Druart 2017-12-27 13:05:45 UTC
Created attachment 70170 [details] [review]
Bug 19883: Add a selenium script to hit all the pages

The idea here would be to catch possible hidden issues, and especially
when the requested data do not exist (for instance hit
circulation.pl?borrowernumber=42 without borrowernumber=42 in your DB).
All these pages must not return 500.

This is not ready at all for inclusion for several reasons:
- Based on existing data (id=1 most of the time)
- DB will be modified
- Not idempotent
- All pages are not covered (TODO)
Comment 2 Jonathan Druart 2017-12-27 13:08:50 UTC
Even if not included it could be useful for QA or RM
Marcel and Tomas, what do you think?
It could be a nice goal to see all these scripts handling non-existing data.
Comment 3 Marcel de Rooy 2017-12-27 13:34:51 UTC
Nice goal on itself. Protecting the database is obviously needed.
Do several scripts need basic parameters at the beginning already (not only what is filled on a form)? So the script needs to know these; could be a maintenance headache?
Comment 4 Jonathan Druart 2018-01-02 16:22:26 UTC
(In reply to Marcel de Rooy from comment #3)
> Nice goal on itself. Protecting the database is obviously needed.
> Do several scripts need basic parameters at the beginning already (not only
> what is filled on a form)? So the script needs to know these; could be a
> maintenance headache?

I plan to test with GET parameters only.