Questionnaire: Evaluating graphical user interface testing tools

About the study
We're studying what things are important for you when evaluating whether a a graphical user interface testing tool is suitable for your needs.

Answering the questionnaire takes approximately 10 minutes. You'll be asked to view a short video of a concept and answer questions based on it.

How we handle questionnaire data
If you choose not to leave your email, your answers will be anonymous. Your answers will be used by the development team in developing a better experience for evaluating Qt Quality Assurance tools.

If you select the option to participate in a further discussion session about the evaluation experience, we will ask your e-mail for setting up a suitable time for the discussion. This links your answers with your e-mail for the development team, but the test results will be reported anonymously.

Your data will be handled according to Qt Privacy Policy: https://www.qt.io/terms-conditions/privacy-policy

Instructions for the questionnaire
Answer the questionnaire from your perspective when you are evaluating whether a graphical user interface testing tool is suitable for a project.

Question Title

* 1. What best describes you?

Management

Team Lead

Developer

QA/testing engineer

Student / Educator

Question Title

* 2. How much experience do you have with graphical user interface (GUI) testing tools (including Squish)?

None

I have heard of them

I have tried out one or some of them

I have worked with some of them

Question Title

* 3. How important following things are to you when evaluating a graphical user interface testing tool? (1=Not at all important, 5=Very important)

	1	2	3	4	5
Project requirements and needs	Project requirements and needs 1	Project requirements and needs 2	Project requirements and needs 3	Project requirements and needs 4	Project requirements and needs 5
Supported technologies	Supported technologies 1	Supported technologies 2	Supported technologies 3	Supported technologies 4	Supported technologies 5
Compability with other tools	Compability with other tools 1	Compability with other tools 2	Compability with other tools 3	Compability with other tools 4	Compability with other tools 5
Tool seems easy to learn	Tool seems easy to learn 1	Tool seems easy to learn 2	Tool seems easy to learn 3	Tool seems easy to learn 4	Tool seems easy to learn 5
Tests can be created by both scripting and recording	Tests can be created by both scripting and recording 1	Tests can be created by both scripting and recording 2	Tests can be created by both scripting and recording 3	Tests can be created by both scripting and recording 4	Tests can be created by both scripting and recording 5
Cross platform testing capabilities	Cross platform testing capabilities 1	Cross platform testing capabilities 2	Cross platform testing capabilities 3	Cross platform testing capabilities 4	Cross platform testing capabilities 5
Comprehensiveness of reports	Comprehensiveness of reports 1	Comprehensiveness of reports 2	Comprehensiveness of reports 3	Comprehensiveness of reports 4	Comprehensiveness of reports 5
Can tool integrate with CI/CD pipelines	Can tool integrate with CI/CD pipelines 1	Can tool integrate with CI/CD pipelines 2	Can tool integrate with CI/CD pipelines 3	Can tool integrate with CI/CD pipelines 4	Can tool integrate with CI/CD pipelines 5
Scalability	Scalability 1	Scalability 2	Scalability 3	Scalability 4	Scalability 5
Price and licensing options	Price and licensing options 1	Price and licensing options 2	Price and licensing options 3	Price and licensing options 4	Price and licensing options 5
Active community	Active community 1	Active community 2	Active community 3	Active community 4	Active community 5
Speed of test execution	Speed of test execution 1	Speed of test execution 2	Speed of test execution 3	Speed of test execution 4	Speed of test execution 5
Low maintenance of tests when UI changes	Low maintenance of tests when UI changes 1	Low maintenance of tests when UI changes 2	Low maintenance of tests when UI changes 3	Low maintenance of tests when UI changes 4	Low maintenance of tests when UI changes 5
I can create tests with my preferred language	I can create tests with my preferred language 1	I can create tests with my preferred language 2	I can create tests with my preferred language 3	I can create tests with my preferred language 4	I can create tests with my preferred language 5
Behavior driven development capabilities	Behavior driven development capabilities 1	Behavior driven development capabilities 2	Behavior driven development capabilities 3	Behavior driven development capabilities 4	Behavior driven development capabilities 5
Availability of support	Availability of support 1	Availability of support 2	Availability of support 3	Availability of support 4	Availability of support 5
What syntax of tests scripts look like	What syntax of tests scripts look like 1	What syntax of tests scripts look like 2	What syntax of tests scripts look like 3	What syntax of tests scripts look like 4	What syntax of tests scripts look like 5
Model based testing capabilities	Model based testing capabilities 1	Model based testing capabilities 2	Model based testing capabilities 3	Model based testing capabilities 4	Model based testing capabilities 5

Other (please specify)

Question Title

* 4. What approaches do you take when evaluating a graphical user interface testing tool?

I read documentation

I create a small test application and test it myself

I follow a short tutorial if available

I browse the website of the tool

I research others' opinions about the toolrk

I look at ready made example projects

I check out a YouTube video about the tool

I study courses online (Coursera, Codeacademy, etc...)

I share the tool with others and ask for opinions

Other (please specify)

None of the previous

We've created an idea about how Squish could be better evaluated in your browser. Please watch this short 4 minute video about the concept. The video shows an example structure of the service. The colors, texts, images or any other content is not final. This serves as a blueprint for further development.

After viewing the video, proceed to answering the next question related to the video.

Question Title

* 5. Page (shown in the video) assists me in deciding whether Squish is worth further evaluation.

Strongly agree

Agree

Neither agree nor disagree

Disagree

Strongly disagree

Question Title

* 6. Please explain your answer to question 5

Question Title

* 7. What approaches do you take when evaluating a graphical user interface testing tool?

Continue reading documentation

Download Squish and test it on my computer

Browse the website of Squish

Research others' opinions about the tool

Examine example projects

Check out a YouTube video about the tool

Study courses online (Coursera, Codeacademy, etc...)

Share the tool with others and ask for opinions

Other (please specify)

None of the previous

Question Title

* 8. We'd love to hear your thoughts further. Can we contact you to book a short online call where you get to comment on a visual prototype of the concept?

Yes