1. Tester can also do troubleshooting, not just developers
2. Getting to the root cause of an issue is not always easy, but i will give some tips to consider in order to succeed

Corina is a senior test automation consultant, with focus on testing by means of Java, Selenium, TestNG, Spring, Maven, and other cool frameworks and tools. Previous endeavours from her 10+ years testing career include working on navigation devices and in the online gaming industry. She loves automation and always tries to learn something new, improving her automation skills and spreading the knowledge to her peers. Apart from work, Corina is a testing blogger (https://imalittletester.com/), a traveler (https://theturquoisecoconut.wordpress.com/), an amateur photographer (https://www.flickr.com/photos/capreoara) and a GitHub contributor (https://github.com/iamalittletester) . She also tweets at @imalittletester.

An issue has been identified in the system. Its’ root cause is very difficult to determine. It is not very obvious how the issue occurs and how it can be reproduced. Somebody needs to spend time identifying the cause, fixing it, and making sure it does not re-occur. But how to do that? Many times people give up after trying a few things that did not yield a result.
The truth is, although it might be frustrating, this task is quite fun. Also, it can be done by testers, because we know a lot about how the systems work and interact with each other, and how our customers use them.
In my talk i will give some advice on how to get to the root cause of a seemingly impossible issue, starting from how to make sure you reproduce it, what are some common things you can check and what tools you have to help you.