In my team we track tickets deviation by using two things:
Jira filters subscription for cases where we need plain(to one person/lead/manager) notification, but without fields analysis
https://github.com/dgroup/lazylead for cases where we need automatically check ticket fields, comments, links and alert corresponding person, assignee or reporter. Please note that i'm author of https://github.com/dgroup/lazylead app.
UAT, ime, should include the complete steps that the actual end user of the app would perform according to your scenarios, from start to finish, and also including expected and actual results in the tcs, e.g.
step 1. open browser/browser is launched, step 2. go to www.blah.com/blah.com is loaded, step 3. click on login field (if you need to get specific) and enter username/field is selected and username is entered.....all the way to the end path you need to test.
You should have performed your functional tests before running UAT cases so you don't necessarily have to validate each field in UAT tcs but make sure you or your team is smoke/functional testing before UAT.
I also agree with the previous poster regarding splitting up your test cases into specific parts which of course depends on what you're doing exactly. TC1_Navigate to Page TC2_Login TC3 Fill PersonalInfo(Or by form section) TC4_Fill IncomeInfo...blahblah.
For each tc after the first one, you can continue from the last tc's step, you don't have to start each test case after #1 from "open browser", and include all the tests together as one test set which will be comprised of the multiple testcases.
perf Profiler for GNU / Linux with performance calculation. https://perf.wiki.kernel.org/index.php/Main_Page
gdb GNU debugger that allows you to "spy" what is happening inside the program during its execution. https://www.gnu.org/software/gdb/
flame graph A graphical profiler. http://www.brendangregg.com/flamegraphs.html
strace Used to diagnose and debug programs under GNU / Linux https://strace.io/
What are triangles?
On both sides:
Isosceles, not equilateral
At the corners: if the function can return a list of features, because they do not exclude those above
Acute (all angles less than 90)
Rectangular (One corner 90)
Obtuse (One angle> 90)
What are not?
a + b == c (degenerate triangle with zero area)
a + b> c
Difference between Test Strategy and Test Plan is as follow:
Test Strategy is written at a high-level mostly by QA Manager which defines the approach of testing. Test Strategy is derived from the Business Requirement Document, it basically sets the standards for testing. Test Strategy contains the following:
Bug tracking approaches
Test Plan is written by Senior/Lead QA which includes details related to testing i.e. how to test, features to be tested, types of testing. Test Plan is derived from SRS. Test Plan contains the following:
Features In/Out Scope
Types of testing