It is possible to use static code analysis tools to figure out which unit tests to run. But is it possible to use (or are there any tools like this?) code analysis for needs of manual testers?

I mean tool wich shows dependencies source code change => area in AUT (from user point of view).

For example: if we have changes in file some.package.reports.EmployeeJournal.java it should notify (by building some report) manual to check the page where we download employee_list.xml. Sure this tool is expected to be tought by human first.

  • "Sure this tool is expected to be tought by human first." What do you mean? AI? Jan 30, 2019 at 12:14
  • @JoãoFarias, I mean just creating links like e.g. "changed file" --> "web-page to test", "changed file" --> "report to test" etc... Jan 30, 2019 at 12:40
  • In many years I've worked as tester both manual and automation, I haven't heard of tester that is using code analysis tool, since the primarily user of these tools are the developers that is intended for component testing and sometimes integration test. May I know the reason why you need to do that though in unit tests?
    – ky-chan
    Jun 24, 2020 at 4:07
  • If it's got a before and after code image to compare, it is no longer static. Some sort of ui impact analysis plugin for the version control system is what this smells like, as long as all of the dependencies are under version control. Oct 23, 2020 at 2:14

2 Answers 2


Maybe this Martin Fowler/Thoughtworks article on The Rise of Test Impact Analysis has some answers. It's about a lot more than unit testing, though. MS VStudio has a feature called "Live unit Testing" that might be similar to your wish.


"from user point of view" is hard to know, because if your suite does not cover the application well, parts of the user accessible code will never be checked.

Now, putting this problem aside, there are some strategies to increase efficiency of test execution:

  • Thanks! But this is all about unit test, not about manual testing. Jan 30, 2019 at 12:38
  • You've mentioned "to check the page". My understanding was that you meant to perform optimized checks. If you testing, you can use the same principles as risk heuristics. But results will probably be not as good, because testing is broader than checking - you would need to incorporate others risk heuristics, focused on your domain. Jan 30, 2019 at 12:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.