Today we had Liz instead of Clare for taking our class because Clare was unwell. I did further work on on the class exercise to define 10 questions I want to answer about my project subject and then I identified 3 good questions from that list of 10 and then I identified the fundamental concept I want to explore.
From there I choose one of the questions and I defined what research methods I would use to answer the question, and a relevant title.
Identify a potential project
Construct 10 (interesting!) questions about your topic
- What automated testing tools are available for free, preferably open source?
- What are the perceived benefits and downsides of these automated testing tools according to other developers?
- What is the perception towards the adoption of automated testing tools from the Koha community?
- What automated testing tools are the easiest for non-developers to learn and use? as some of the Koha testers are librarians who do not know how to code
- Would the adoption of automated testing tools speed up the Koha bug workflow?
- What is the most suitable automated testing tool for Koha?
- Are there automated testing tools that test if patches meet the project’s coding guidelines, i.e. not just testing functionality?
- Which of the tools use a record/playback or manual coded test case development?
- Does the automated testing tool use a model-based testing?
Identify three good questions/ideas. For each of these 3 suggest what you could do to answer/explore it.
- What automated testing tools are available for free, preferably open source? Secondary research to identify the range of free automated testing tools available
- What is the most suitable automated testing tool for Koha? Primary research using exploratory research specifically a comparative study. I will write/create test cases for a variety of automated testing tools to test a variety of Koha patches and will compare how each performs to identify the best performing tool.
- Would the adoption of automated testing tools speed up the Koha bug workflow? The answer for this question leads on from question 2 because each patch that I test using a automated testing tool will have the time it takes to test recorded and this will be compared against the time it takes to manually follow a test plan.
What is the fundamental goal underlying each of the 3 questions?
To find a suitable free automated testing tool to use in the Koha project that is both easy to use (so it’s use isn’t restricted to developer testers) and speeds up the Koha bug workflow.
- Making a choice
- Choose one of the questions and make a more detailed description of what you would do to answer/explore the question i.e. a first draft of your list of activities
What is the most suitable free automated testing tool for Koha? This will be answered through performing secondary research from academic journals, industry whitepapers, and online courses to identify the available free automated testing tools.
Followed by exploratory research method (which is a primary research method) to write/create a test case for each of the identified tools to be run on 3 different patches from the Koha bugtracker (known as Koha BugZilla). The time and ease to write each tools test case and then run the automated test will be recorded. Then each of the 3 patches will be manually tested by me to give a time and ease comparative value for manual testing.
The fastest and easiest to use automated testing tool will be able to be identified from the comparative study. Therefore I will have identified the most suitable tool for use in the Koha project. I will promote this tool to the Koha community through the #koha irc channel, and mailing list.
Also this suitable tool will be compared against the time/ease to performing each of the three patches manually and so I will be able to identify if the use of an automated testing tool for patch testing (regression testing) would be useful for the Koha project
- Write a title for this possible project.
Identification and justification for the use of the most suitable automated testing tool for the Koha Integrated Library Management System (ILMS) project.