Hello! Im excited to get my new career going in software testing. I recently finished a training course in Python programming and Software testing and have an ISTQB certificate.
To gain some first practical experience, I want to help Krita however I can.
Is there any professional software tester here who can help me onboard and getting to know the project and work a bit?
Im thankful for your help!
Welcome. You have a very good idea. Let’s call @Michelist he knows his way around here well and maybe he can tell us.
Добро пожаловать. У Вас очень хорошая идея. Давайте позовём Michelist он хорошо здесь ориентируется и возможно подскажет.
Thank you for pinging me @Dima!
Hello @Zodd and welcome to the forum!
I don’t think we have anything like a professional software tester here, but that doesn’t mean we couldn’t use someone like you here, probably just the opposite.
However, because of your question, I’m not sure if you are aware of the “size” of the Krita project? Krita is, despite its size and 25-year history, a project that is managed by only a few full-time developers, currently five if my numbers are still correct, plus a few volunteer programmers who are very close to the team, as well as programmers who are loosely connected to the project, i.e. who are friends of Krita and use Krita themselves, who contribute code to Krita.
Then we have access to the nightlies, i.e. the pre-versions of Krita, which are always open to every volunteer and which you can find here:
The Krita Plus versions are the current release versions plus all patches and additions that are considered relatively ‘stable’, but have prealpha-status:
The Krita Next versions are the more experimental versions of Krita, in which things are checked and tested, these are not meant to be used in any productive environment:
Since you have posted in the right forum area, there is a good chance that your contribution will be noticed by the developers sooner or later, as they visit here sporadically.
Maybe @YRH, @freyalupen, @Lynx3d can also say more about this. If you would like to get involved yourself, you can search for contacts in the IRC channel #krita at https://web.libera.chat/.
Michelist
Thanks for your really quick and insightful responses! I will take a good look at this and eventually get in contact on IRC.
Since Im new to this all and the last time I painted anything was on canvas 15 years ago, I will first get to reading all the documentation I can find and get a feel for the project. 
Its nice to hear its a small community, as I feel overwhelmed when Im looking at other, big open source projects, so thats fine for me!
Hi, it may be helpful to read this topic and the instructions within. This is the type of help the developers need from time to time.
Basically, confirming the bugs are real and reproducible is of great help. After that locating the regression commit is the best thing. All that info can be added to bugs in the KDE tracker and will help substantially.
Welcome, @Zodd !
Thanks for all of the awesome information! It took me a while to get into it, but I have now read through the bug hunt project and the bug triaging guide, aswell as created an account for the bugtracker.
I installed a few different build versions including the debug packages and Im looking at the bug list to find a component/environment that I feel confident starting on, any tips on that?
Im thinking about starting with a specific tool, I saw the text tool has quite a few reports, so Ill take a look into that!
edit: btw I didnt notice most people use their name abbreviations as their usernames, is there any way I can change that? Unless Zodd is fine for you, you an also call me Lukas.
@Zodd: If you want to change your username, you simply need to ask our moderators / administrators. To ask them, you need to ping them, like I pinged you at the beginning of this posting ( @Zodd ) . Here you need to ping @ sooz and @ raghukamath but need to remove the space I put behind the @-sign.
Michelist
Alright, thanks for the tip, if theres no common naming convention, Im also happy to keep the username as is.
So now I confirmed my first bug!
I took a look at this one: 502590 – Text Tool Save Dialog Does Not Disappear and Text Resizing Not Working
A few questions I got about that: wheres the line between feature request and a bug if a report concerns (improving) an existing feature not working as expected? As for this specific example, I first wasnt sure if the selection tool is supposed to be used to transform text, but when looking at the 5.3.0 pre-alpha I noticed the tool being improved and it seems like those functions are being worked on.
I hope I did everything correctly with setting it to confirmed. I’m thankful for all advice and will get back to it tomorrow!
Lukas
The Text Tool is in the middle of being completely rewritten for 5.3, so triaging reports for it will be tricky. You might want to pick a different component to check out.
That particular bug report has two or three different unrelated issues listed which should be separate reports.
Alright, thanks for the info!
Thats what I suspected already. Is there a kind of backlog/user story catalogue where I can check what is currently being worked on? Just to avoid these issues at the moment.
And I also thought about the report being a bit convoluted with those 3 seperate anomalies mentioned.
What would be the best way to treat reports like that? Split them up and create seperate reports myself, then close the original one and link to the new ones?
Lukas
There’s not really any kind of roadmap, just the development news posted on krita.org. The Text Tool is the only thing being majorly worked on right now, aside from the Qt6 port which isn’t relevant to the bugtracker yet.
For a report with multiple issues, KDE’s guidelines suggest to close it with an explanation that bug reports should only contain one issue. If you think any of the issues are worth reopening a report about then you could also do that.