Download as PDF, PPTX
Uploaded byAlan Richardson
If you want to automate, you learn to code
The document discusses the importance of automation in coding, emphasizing the distinction between tactical and strategic automation. It provides insights on selecting tools and programming languages, as well as transitioning from tactical solutions to more maintainable strategic approaches. The key takeaway is to learn how to effectively use and extend tools while continuously improving automation skills to add value in various processes.
More Related Content
Similar to If you want to automate, you learn to code
If you want to automate, you learn to code
- 1. If you wantto automate, you learn to code - and you learn to code well
- 2. Fast paced summaryof what we are going to cover insert fast paced summary here :)
- 3. Alan Richardson • www.javafortesters.com •www.seleniumsimplified.com • www.eviltester.com • www.compendiumdev.co.uk • uk.linkedin.com/in/eviltester • @eviltester
- 4. "Automate" doesn't mean "AutomateTesting" • dictionary.com/browse/automate "to install automatic procedures, as for manufacturing or servicing;"
- 5. You don't needto 'code' to 'automate' We can Automate by adding tools
- 6. I use Tools -FTP - Text Editors - etc.
- 7. We take 'tools'for granted Because we use them so often
- 8. So its worthinvestigating: • what tools are you using? • capabilities of your current tools • alternatives to your current tools
- 9. There are some processeswe have to automate And someone else might have automated them already. That's a tool.
- 10. But tools comewith limitations
- 11. Requisite Variety "Only varietycan destroy variety" - Ross Ashby en.wikipedia.org/wiki/Variety_(cybernetics)) "Only variety can absorb variety" - Stafford Beer
- 12. Strategy #1 -Build a toolbox with Multiple Tools
- 13. There is adifference between 'Strategic' and 'Tactical'
- 14. Automate Tactically solve aproblem quickly Automate Strategically solve a problem for the long term
- 15. Toolbox building is 'Strategic' Along term strategy to identify tools. And I have to commit to this.
- 16.
- 17.
- 18. Finding Tools canbe a Tactical pursuit If I learn how to find tools. I can find tools when I need them.
- 19. Finding Tools when youneed them Is also a key step in learning how to automate.
- 20. How do wefind tools? • What are you trying to achieve? • learn the domain language for the task • Narrow by technology? • technology used • technology tool implemented in
- 21. Non-domain specific task Search: "Iwant to copy a document to another machine" learn: server, transfer, file
- 22. Domain language for task Search:"Tool to transfer file to server" learn: ftp, scp, sftp, ssh protocol, login, user account
- 23. Specific Technology "What doesmy specific server use?" "What do I use?" Search: "Windows Software to transfer file via scp ssh key"
- 24. Building these queriesand chaining them is a skill • the more we learn the better we get • the better we understand the technology, the faster we find what we need • technical staff take this skill for granted • we also use this skill to find - IDE, Libraries, Build Tools, etc.
- 25. Extend tools Assuming thatyou can find tools Favour tools that support extension Learn the Extension possibilities for your chosen tools
- 26. Scripting a toolis an easy way to learn to code
- 27. Tool Chaining Don't underestimate the power of the command line On Windows and Linux
- 28. And now forthe meat of of it "Give a man a fish you feed him for a day. Teach a man to fish then you feed him for a lifetime."
- 29. The Ultimate Aim "Givehumankind the power to summon forth fish from the empty air"
- 30. Learn to codeand write our own
- 31. When people learnto code they focus on programming language IDEs build process 'making programs'
- 32. We don't always 'makeprograms' when we automate
- 33. Pick your programming language forthe right reasons
- 34. 'Easy to learn'? 'Easyto run code'? 'Easy to cobble together stuff that runs from copy and pasted examples off the internet'?
- 35. How to makeJava Easy to run Write an @Test method that does stuff Run the @Test method Tadah!
- 36. So how dowe pick a language? • what is your system written in? • what languages do people that you can ask for help know how to code? • what examples have you found that do what you want to do? • what tutorials or books have you found that you like?
- 37.
- 38. "Test Automation" -Automating Strategically • long term • paths through system
- 39. Automate Tactically • Automateto save time • Automate to make your process more repeatable • Automate to help you, or someone else
- 40. Tactical Solutions MightBecome Strategic • Maintainable • Abstraction Layers • Tested
- 41. Strategic Solutions canbe used Tactically • Adhoc exploration using abstraction layers • Temporary Data Exploration
- 42. Automate Tactically With •Tools • Chaining of Tools • Scripting languages using tools and libraries • @Test method using libraries
- 43. Warning - TacticalSolutions might not translate to Strategic Solutions without work • the tactics we choose might not scale • unreliable interaction • time based synchronisation • hacky code
- 44. Danger - OpportunityCost • Some people view "Testing" as an opportunity cost of increased strategic "Automating" • We could also consider "Not improving your ability to automate" an Opportunity cost of not automating strategically
- 45. We can refactor tacticalsolutions into strategic solutions if we chose appropriate technology
- 46. Examples of movingfrom tactical to strategic Can't 'show you' many because: • a lot of this is commercially sensitive • very domain and project specific
- 47. How do Itend to build tactical solutions? I can tell you that: • I tend to use Java, not a scripting language • Because... libraries, maven, JUnit • ... I know it well
- 48. And now anExample Pandocifier
- 49. Automate Tactically • batchshell scripts to automate pandoc • pandocifier to run leanpub through pandoc Refactor to Strategically Automated • review, plan, refactor • keep it working as a tactical automated solution
- 50. Review Pandocifier • Refactorto domain objects • Execute Pandoc • Inject Configuration • Externalise Configuration • External Pandocifier Object • Build into app
- 51. Refactor to domainobjects • There is one domain object - BookTxtFile • If I refactor to domain objects • fewer comments in the code • fewer lines of code in tactical solution • e.g. PreviewMdFile, BookDetailsContentReader • write Unit tests for the domain objects
- 52. Execute Pandoc Instead ofwriting out instructions to the user to execute 'tactic'. // output the command to generate the book to console System.out.println( "pandoc leanpubpreview.md -f markdown -s " + "-o leanpubpreview.pdf --toc"); The code could execute them: Process p = Runtime.getRuntime().exec ("pandoc leanpubpreview.md -f markdown -s " + "-o leanpubpreview.pdf --toc")
- 53. Inject Configuration Instead ofhardcoding paths and file names (possibly pandoc arguments) I could create a PandocifierConfig object with getInputFilePath() and getOutputFileName()
- 54. Externalise Configuration Mechanism tocreate the PandocifierConfig from a file • Properties file - easy to read with standard Java • text file - write a parser • JSON file - need an external library
- 55. External Pandocifier Object •could create Pandocifier from @Test injecting config • new Pandocifier(config).createPDF()
- 56. Build into app •create a main method with params that setup config • use mvn package to create a .jar file • use java -jar pandocifier.jar to execute • add to path and run from anywhere
- 57. Prioritise the 'ideas'to maximise tactical advantage • Refactor, Execute, ... • Inject Config, Execute Pandoc, ... • Externalise Configuration, Execute Pandoc ...
- 58. Decide Prioritisation • InjectConfig, • Execute Pandoc, • Pandocifier, • External Config find the code to support this decision on github
- 59. Walkthrough of Changesfor Config • Create object to model config - store, not transfrom • I Know that 'if' I create a main later, I can still use this • Move the 'hard coded' stuff into an object • Add it to an @Before to 'simulate' injection • Possible future need for a PanDoc configuration see LeanPubConfigTest.java
- 60. Walkthrough of Changesfor Execute • Initially Runtime.getRuntime().exec("..."). • Execution errors • Rather than debug it I moved to ProcessBuilder • New config for the setPandocPath • Added opened output folder - new automated time saver see LeanPubPandocConfigExecuteTest.java
- 61. Walkthrough of Changesfor Pandocifier Object • I create an internal class called Pandocifier • construct it in the @Before with the config • amend the @Test to use a Pandocifier createPDF • automatically create the createPDF • copy paste the @Test code into createPDF see LeanPubPandocConfigExecuteObjectTest.java
- 62. Walkthrough of Changesfor External Config • Use new @Ignore @Test to create a property file • Create a property file reader that returns a config as an internal class • Now the createPreviewMVP @Test method looks like a main method see LeanPubPandocConfigExecuteObjectPropertiesTest.java
- 63. Make it anApp • create a main method, call from @Ignore MVP @Test • move the inner classes out to main packages • change the pom.xml to have a build section for the mainfest • delete previous 'refactoring tests' • mvn package • because it is being released on github removed the 'leanpub' from .jar so people don't think it is official
- 64. Retrospective • always keptthe tactical mvp class running and available • refactored to strategic solution • inner classes until used by multiple classes e.g. main and MVP • final strategic solution 'wrapped' as a 'tactical' @Ignored test • didn't add many new features, didn't 'test', still a lot to do if 'other' people want to use it • but now I can add it into CI for my local builds
- 65. Final Thoughts • Automatetactically vs automate strategically • Use of Tools • Learn to program by extending tools • How to choose a programming language • How to move from tactical to strategic
- 66. Learn to codewell • still lots to learn, but its fun • Abstractions • Domain Driven Design • Test Driven Development • Design Patterns Whatever you do. Make it add value.
- 67. Alan Richardson • www.javafortesters.com •www.seleniumsimplified.com • www.eviltester.com • www.compendiumdev.co.uk • uk.linkedin.com/in/eviltester • @eviltester