Skip to content

Manual testing overview

Igor Korsukov edited this page Feb 9, 2023 · 1 revision

Manual testing

Manual testing is one of the main ways to test applications in general, so it is very important to achieve a high-quality application.

Manual testing can be separated into two large parts - checking functional requirements and checking user workflows (test cases). For example, we want to test the creation of a new score. We can test the user workflow, that the user can open the dialog for creating a score, select instruments, and when you click on "Done", a created score will open. And we can also test functional requirements, for example, that the added instruments are placed in a certain order.

We do manual testing for most pull requests, as well as once-a-week review testing (smoke test) and more rigorous testing before the release of the production version.

Manual testing is a very time-consuming process, it takes a lot of effort and time. For testing to be more effective, it is necessary to describe test scenarios (checklists) and functional requirements. Also, in order to facilitate the process of manual testing, we are developing tools for test automation that allow us to write scripts that imitate user actions, thereby passing the test scenarius automatically.

Testing

Translation

Compilation

  1. Set up developer environment
  2. Install Qt and Qt Creator
  3. Get MuseScore's source code
  4. Install dependencies
  5. Compile on the command line
  6. Compile in Qt Creator

Beyond compiling

  1. Find your way around the code
  2. Submit a Pull Request
  3. Fix the CI checks

Misc. development

Architecture general

Audio

Engraving

Extensions

Google Summer of Code

References

Clone this wiki locally