Near Future of Programming Languages [pdf]
One area I haven&#x27;t seen any good solutions for is the interleaving of tests with production code.  I think we need better ways to express tests without cluttering the production code and excessive mocking.  What I&#x27;d like to do, and really can&#x27;t in any language&#x2F;tooling that I know of, is to extract some arbitrary subset of the code and surround it with tests or a test harness.  I&#x27;d also like to specify various injection points for tests right as I&#x27;m writing the code in a way that doesn&#x27;t affect the production code and contributes to its readability.  Perhaps this is pieces of server and client code or various services all tested together.  When I refactor the code I want the tests to &quot;refactor&quot; with the code.  I don&#x27;t want to need to rewrite my tests...  Automatic test generation is another interesting area (beyond the basic table or algorithm stuff we might do in tests today).<p>It&#x27;s almost like the &quot;problem&quot; isn&#x27;t the languages themselves, it&#x27;s the tooling around the languages.  I want to be able to do a lot more than &quot;compile&quot;, &quot;run&quot;, with my code...  I can imagine machine learning driven tooling being able to automate a lot of the mechanical aspects of code writing beyond the simple generate a closing bracket that an IDE can do...