Testing Heidisql

Hi, I use Heidisql and for now, this is the best DB tool that I used. I'm a QA and I loud like to help with testing it. I'm not sure how much time I can spend but I like the project and I want to help for free.

That's nice!

There's the bug tracker on Github, which shows roughly 300 open issues, and some of them need more attention than they get yet. Maybe you browse through the issues and make some recommendations for the releases? Releases are called milestones on Github. The only open one is currently the v10.3, which I plan to release later this year.

OK, I will check the needs-info and tickets that involve crashes so I will try to provide more information.

If there is some other area that I can check just tell me.

There are also issues which were never updated, without any label.

Ok I'm on it I will try to clear as much as I can them this weekend

Hi, this is the report there are 3 tickets that I manage to reproduce with the steps from the description.

https://github.com/HeidiSQL/HeidiSQL/issues/195 --- it's reproducible we can override shortcuts with no warning https://github.com/HeidiSQL/HeidiSQL/issues/503 --- it's reproducible if we rung long query is one tab and HeidiSQL is locked until its finish

https://github.com/HeidiSQL/HeidiSQL/issues/437 --- it's reproducible When we clone user from existing one The fields:-are empty Password: Repeat password: After we click save we get the message in the bottom right that says: "The user has an empty password" Maybe this is misleading that the user won't be generated but it still is.

Thanks for looking into these tickets. Could you please post comments into the tickets itself, so we have them in the right thread. This forum thread is more a "meta-thread".