I'm happy to announce a project I've been working on for a while now:

, the open crowdsourced user testing suite

OPEN-CUTS is a web-tool to help communities with user testing! The goal is to allow even inexperienced users to easily report test results for new software releases. OPEN-CUTS then aggregates and compares the metadata across versions to identify regressions.

It's still early in development, but the basic features are there! We'll begin trialing the software for different @ubports projects such as , the , and some core apps. Head over to to see it in action!

Again, development is still early, so head over to our GitLab org to see how things progress over there (and maybe star the repos while you're at it?). I also probably won't shut up about it on here ;)

Show thread

The backend server is written in and provides a API built with the awesome library. Data is stored and aggregated in a database, accessed using the library.

The web-UI is a single-page-application built with . It uses the GraphQL client to consume the API.

Show thread

Things are going to get interesting, i promise. We're currently toying around with the idea to have the @ubports installer automatically report results if the user opts in ( There's some great potential there, i think!

Show thread

:) This looks good.
Is it for feature requests as well as bugs? :o) was that a feature request?? ;)

@mark Thanks! Currently this is only for releases. OPEN-CUTS picks up new versions from the Ubuntu Touch system image server channels, GitHub or GitLab releases, or the OpenStore (more sources in the future). So you can, for example, check if the latest release candidate of has any failing tests before publishing a stable release.

@mark I thought about adding support for specific testing requests, so you could test if a patch fixes a bug or a feature-request was properly implemented, but that's still in the planning stage. Was that your question?

As an example: this week there was an update to the calender. (So I know it's being maintained, but not by who, or where to file a feature request). I'd thought that a ToDo list component would be useful and apt, since it uses all the same resources. I ended up putting the idea on the forum... Not the best place for it.

@mark Forum is good as well, as you can get some additional input there and brainstorm together with other community members. In the end, the place to be is the issue tracker, which would be for the Ubuntu Touch calendar app.

Most apps on the OpenStore have a support link, which takes you to the correct tracker. For example on the calendar app:

:) I like the calendar app - It's good as a note-taking device in meetings (as it sets time and date), and it's also good as a daily journal.

:) Not having to think about where to report bugs streamlines the whole procedure: a much easier process. Good work!

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!