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

Move test suite to another repository #252

Open
rodarima opened this issue Aug 20, 2024 · 2 comments
Open

Move test suite to another repository #252

rodarima opened this issue Aug 20, 2024 · 2 comments
Labels
design Related to design problems test

Comments

@rodarima
Copy link
Member

Our current test suite involves a very limited number of simple HTML rendering
tests. These tests are currently distributed in the tarball release.

However, there are other tests we should be doing which would involve many other
pieces that we don't use for Dillo:

  • HTTP, HTTPS, FTP, Gopher, Gemini, and other servers
  • Multiple TLS ciphers (including broken ciphers or bad behaved replies)
  • Multiple compression algorithms for transfer encoding
  • Multiple content type mismatch (Content-Type says PNG, image bytes say JPG)
  • Very slow networks and missing packets (TLS timeout?)
  • Performance tests: measuring how long it takes to render some pages
  • Memory tests: tracking memory usage over time and potential leaks

All those tests will likely require extra software dependencies that would cause
Dillo to have a unnecessary long list of dependencies for testing.

Having tests in a separate repository allows us to test multiple releases of
Dillo with the latest test suite. We could even try to run WPT or port some of
the tests to our test suite.

Moving them outside the repository also makes the Dillo repository smaller, as
we don't have to bring unnecessary images or other potentially big files with
the browser.

The drawbacks of this approach is that we won't be able to simply run make check to pass all tests in any platform.

We can develop Dillo from an old machine too, as the current requirements to
build it are not too high. Ideally we should keep the requirements for both
using Dillo and developing it about the same.

This would also lift the strict requirements to stick to old C and C++ standards
for Dillo code, but allowing them for testing.

This can be tested without disrupting the current test suite distributed with
Dillo, and then decided once we have more information on how that would work
out.

@rodarima rodarima added design Related to design problems test labels Aug 20, 2024
@sjehuda
Copy link

sjehuda commented Nov 6, 2024

Gopher and Gemini would absolutely be great to have!

@rodarima
Copy link
Member Author

rodarima commented Nov 6, 2024

Read the issue again.

Gopher and Gemini would absolutely be great to have!

https://dillo-browser.github.io/#plugins

Locking.

@dillo-browser dillo-browser locked as spam and limited conversation to collaborators Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
design Related to design problems test
Projects
None yet
Development

No branches or pull requests

2 participants