tingtun/user-testing-tool

Combines user testing with automated testing services to improve the accessibility and usability of web sites.

user-testing-tool's Issues

Access eGovMon Checker database and WAM from backend instead of using JSON export

Tweak design

Use eGovMon color scheme. Consider making the navbar and test UI look like one component by having the same background color. Move progress bar to navbar.

Do not render raw HTML in questions in test view

Enhance keyboard support

Add support for testing videos

Hide instead of dim automated checker results in result view when option is set

Highlight element that is currently tested

Fix backend issue

error=null
result=[object Object]
body=undefined

/var/www/no.tingtun.utt/backend/main.coffee:96
if (result.body.substring(0, 19) === 'An error occurred: ') {
^
TypeError: Cannot call method 'substring' of undefined
at Request.io.sockets.on.socket.on.fs.readFile.socket.emit.locale as _callback
at Request.init.self.callback (/var/www/no.tingtun.utt/backend/node_modules/request/main.js:122:22)
at Request.EventEmitter.emit (events.js:99:17)
at Request. (/var/www/no.tingtun.utt/backend/node_modules/request/main.js:661:16)
at Request.EventEmitter.emit (events.js:126:20)
at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer (/var/www/no.tingtun.utt/backend/node_modules/request/main.js:623:14)
at IncomingMessage.EventEmitter.emit (events.js:126:20)
at IncomingMessage._emitEnd (http.js:366:10)
at HTTPParser.parserOnMessageComplete as onMessageComplete
at Socket.socketOnData as ondata

Prevent backend from crashing when getting different types of errors

Present more details in results view

Might extend the row or have a tooltip-like widget.

Create a view for the H1 heading

Wrap the h1 tag in its own view. Consider giving it a model that holds the current content of the h1 and fires an event when the content is change. Then the view can listen for that event and update itself accordingly. Also another function can listen for the same event and change the document title as the h1 changes.

Integrate with FAQ

Make it possible to export to tagged PDF, Excel, … for offline use

Require answer before clicking “Next”

Add feedback button

The button should be shown on the right side during the testing period for 0.3.

Consider using a fixed position for answer buttons

Refactor result view and test run model

Allow user to specify URLs without protocol

Present automated test results

Reduce mouse movement

Implement remaining “to be verified” tests

Make it responsive

Test it on as many phones as needed.

Simplify deployment process by having a configuration file

Make it possible to change the flow of a test run

Specifically, we want to avoid running the same tests over and over, as this is often caused by a bug in the CMS used on a page.

Add loading indicator

Ensure that UTT works for sites that has no “to be verified” results

Group similar tests

Test a complete website instead of only a web page

Make it possible for the user to change the appearance of the UI

Add support for testing alternative text belonging to images

Run the backend using nodejs instead of coffee

Use coffee to convert backend/main.js from CoffeeScript to JavaScript, and tweak the deploy.sh shell script to run this using nodejs instead.

Add translation support

Add GitHub Issues link to home view

Minify JavaScript and CSS

Add link to eGovMon Checker in result view

Integrate results page with eGovMon Checker

Investigate possible race condition when loading JavaScript libraries

Temporarily hide submit button

Enable users to see the line of sourcecode corresponding to the line numer in the result view

HTML source code viewers may render the source code differently.
Supplying the actual source code that triggers a "fail" might be useful.

Such a source snippet could also highlight the corresponding tag/class/id.

Render views only when necessary

Stop all views from rendering when the application starts. Currently a set of test results is being un necessarily rendered using the default webpage. Render each view only when it's required.

Detect answer patterns and “user test” if the pattern matches in other contexts

The intent is to minimize the amount of input needed. The pattern can be associated with a user. This requirement needs to be further specified, and it would be beneficial by providing an example.

Only allow changing web page to test on first page

Serve web page to become tested through proxy

This allows for tracking user activity such as mouse clicks, highlighting elements, disabling JavaScript redirects, …

Support use of multiple tabs

This requires storing more state data on the server.

Use CDN for external libraries

Enable user to mark alternative text as non-descriptive

They should be learned by the system.

Do not user test invisible elements

Store test results in database

Do something after user has pressed “Submit results”

Make utt.tingtun.no point to UTT