You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried using Pinta for editing tasks, and I regularly encounter severe bugs that make it unusable, e.g. ctrl-z swapping content between layers or creating a layer only for it to be entangled with another layer. It looks like the test suite does not have GUI tests to ensure that the whole application is behaving properly. Given that the most pervasive classes of bugs that have impaired usability in my experience are state transition bugs from edit history and layer bugs, it makes sense to me that some kind of automated GUI tests (or non-mocked tests of these subsystems) would help surface underlying issues and improve maintainability.
I'm not well versed in image manipulation in C# (it has been several years since the last time I contributed to any C# codebase), but it should be doable in theory -- and if it isn't for some reason, that is probably indicative that a refactor is needed. Also, I have only used Pinta in Linux; it is possible that these issues are due to underlying platform compatibility problems with Dot Net rather than this codebase, which a more comprehensive test suite probably would not help resolve.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hey all,
I have tried using Pinta for editing tasks, and I regularly encounter severe bugs that make it unusable, e.g. ctrl-z swapping content between layers or creating a layer only for it to be entangled with another layer. It looks like the test suite does not have GUI tests to ensure that the whole application is behaving properly. Given that the most pervasive classes of bugs that have impaired usability in my experience are state transition bugs from edit history and layer bugs, it makes sense to me that some kind of automated GUI tests (or non-mocked tests of these subsystems) would help surface underlying issues and improve maintainability.
I'm not well versed in image manipulation in C# (it has been several years since the last time I contributed to any C# codebase), but it should be doable in theory -- and if it isn't for some reason, that is probably indicative that a refactor is needed. Also, I have only used Pinta in Linux; it is possible that these issues are due to underlying platform compatibility problems with Dot Net rather than this codebase, which a more comprehensive test suite probably would not help resolve.
Just my two cents.
All reactions