Metaprogramming, Machine Learning, and Automated Testing: Back to the drawing board

Why am I rage-quitting on AST parsing for compositional breakdown?

Rule of Three — never create “abstraction layers” before you have three independent cases

  1. Create a basic composite breakdown of the classes I analyze. I don’t care how I get there.
  2. Use Tensorflow’s Java API to start collecting and analyzing data to questions such as “what tests pass?”, “what tests fails?”, “what is the nature of the failing tests?”, “how complicated are the functions that I try to test?”.
  3. Solidify and generalize my basic groundwork for detecting UI controls. What I have is works, but it needs to act as an independent module from the project. Same goes for compositional breakdown and the future machine learning portion.

In the meantime

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
mvndy

mvndy

software engineer and crocheting enthusiast