What is "STR" and how do I provide it?
STR - Steps to Reproduce - is basically a description of how to provoke an error or bug so we can reproduce the same error or bug in our environment.
We have the possibility to set up most environments that DME encounters, and can therefore use STRs to verify a bug if it exists or pinpoint where the problem is and get the problem solved faster.
STR example of a DME Client that crashes
This is an actual STR from a bug in a Symbian device that caused the DME Client to crash:
- Install the DME client on the device, enter username and password
- Confirm the server path
- Confirm verify password
- Confirm import emails from server
- After email sync is done, do a full calendar sync (replace from server)
- Open a calendar Item that has come down to the device from the client
- Client crashes and exits out to Symbian desktop
- DME client needs to be launched again after this.
This simple 8-step STR gives Excitor the information to reproduce the bug and find the error.
Additionally it will always help to enable debug on the DME Client as the log can/will most often tell what the problem is, but the normal log will not as the cause of the problem is not in the code that outputs information to the user or to the DME Server.