Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse 4diacWiki/Development/User Interface Quality Improvement"
(→Topic) |
|||
| Line 1: | Line 1: | ||
=== Topic === | === Topic === | ||
Eclipse 4diac IDE User Interface Quality Improvement Through Automated Testing | Eclipse 4diac IDE User Interface Quality Improvement Through Automated Testing | ||
| + | |||
| + | Often open source projects have only a few contributors. These try to incorporate all new ideas and improvements. However, this leaves little time for testing, which means that the software quality suffers. Since Eclipse 4diac is also still tested manually, which on the one hand is inefficient and on the other hand is often not performed completely due to time constraints. For this reason, an automated test set for the 4diac IDE user interface would be a good improvement. | ||
| + | |||
| + | Contributer: Andrea Zoitl | ||
| + | Timeline: May - November 2023 | ||
Revision as of 09:47, 22 June 2023
Topic
Eclipse 4diac IDE User Interface Quality Improvement Through Automated Testing
Often open source projects have only a few contributors. These try to incorporate all new ideas and improvements. However, this leaves little time for testing, which means that the software quality suffers. Since Eclipse 4diac is also still tested manually, which on the one hand is inefficient and on the other hand is often not performed completely due to time constraints. For this reason, an automated test set for the 4diac IDE user interface would be a good improvement.
Contributer: Andrea Zoitl Timeline: May - November 2023