Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Scholia automatically for a set of test pages #990

Open
Daniel-Mietchen opened this issue Dec 9, 2019 · 3 comments
Open

Run Scholia automatically for a set of test pages #990

Daniel-Mietchen opened this issue Dec 9, 2019 · 3 comments
Assignees
Labels
documentation hopefully helpful explanations of how things work examples usage examples presented to Scholia users performance the way Scholia treats the machines using it

Comments

@Daniel-Mietchen
Copy link
Member

Some useful starting points here would be

@Daniel-Mietchen Daniel-Mietchen added examples usage examples presented to Scholia users documentation hopefully helpful explanations of how things work performance the way Scholia treats the machines using it labels Dec 9, 2019
@Daniel-Mietchen Daniel-Mietchen added this to To do in Meta via automation Dec 9, 2019
@nunogit
Copy link

nunogit commented Dec 17, 2019

@Daniel-Mietchen regarding this topic, I came across Selenium. I used it a couple of years ago, and I didn't even remember it until I came across it again.

Pro's: renders javascript, which would be great for us. Drivers for several browsers (although chrome is the one best supported).
Con's: it's slower than most frameworks when crawling/testing for errors.

Do you know it? If so, what do you think?

@nunogit
Copy link

nunogit commented Feb 3, 2020

DataTables on pages are now being tested.

Code:
https://github.com/nunogit/scholia-junit-selenium

CI / automated testing
https://travis-ci.org/nunogit/scholia-junit-selenium

Next steps:
Now that the basic infrastructure is set, the next steps are:

  1. extend to test other widgets
    1.1 improve the way widgets / DataTables fail, to be easier to detect failures Improve the way a query fails(table or Iframe) #1026
  2. Make a list (or dynamic list) of pages to test Create test set of pages (URI's) #1033 / https://www.wikidata.org/wiki/Wikidata:WikiProject_Scholia/Testing

In parallel test this against a proxy and/or with in-page optimization and assess if the failure rate decreases. Issues: #1024, #67 and #1012

@Daniel-Mietchen
Copy link
Member Author

I just added some examples but think this flat file with just the Wikidata URLs is a bit hard to manage in the long run. What about using a Wikidata page as a source for the tests, e.g. something similar to but more machine friendly than https://www.wikidata.org/wiki/Wikidata:WikiProject_Scholia/Testing ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation hopefully helpful explanations of how things work examples usage examples presented to Scholia users performance the way Scholia treats the machines using it
Projects
Meta
  
To do
Development

No branches or pull requests

2 participants