We have a windows desktop client(a branched version from main branch) 2-tier software that uses data source in sql server. I'm supposed to do system testing for this software at work.
The software is a product/order/component catalogue software that contains information about computer models hierarchy with components that are suitable for that models. Each models can also be tracked to orders, and orders can give details about the computer model and specific components that the computer is configured with.
We have three types of users and each users have different access rights. For example, admin can create new users. Users could be viewer and editor. Editor have read&write access. Viewer have only read access.
I'm kinda new to software testing. But I'm thinking since it's system testing. That I should:
-using created editor to create an item.
-using the editor account to create an order containing this item.
-using a viewer to view the order.
-using the editor to delele the order.
-using the viewer to search for the order or component and assert that order is gone but component is still there.
-checking in the database if the order is removed but the component is still there.
Could this be a good start for a system testing for this application?
Also, is there a way or strategy to automate tests somehow? We might have access to QTP.