base on A set of principles, practices, idioms, and strategies pertaining to automated software testing and its adoption ## Automated Testing Playbook A set of principles, practices, idioms, and strategies pertaining to automated software testing and its adoption. **WORK IN PROGRESS:** This material is currently in draft form and under active development. See [the GitHub issues page](https://github.com/18F/automated-testing-playbook/issues) to examine progress. This guide is a distillation of the principles found in Mike Bland's [Unit Testing Perspectives](href="http://goo.gl/eE8IUw) presentation, licensed under [CC BY 4.0](http://creativecommons.org/licenses/by/4.0/deed.en_US), based on a high-level outline by Mike and Dr. Robert Read of 18F. It also contains content copied directly from several of [Mike's personal blog posts](https://mike-bland.com/)</a> as well as some of his posts on [AutoTest Central](http://autotestcentral.com/)</a>; both blogs are also licensed under CC BY 4.0.</p> This playbook is divided into five sections: ### [Automated Testing Roadmap](pages/roadmap.md) A roadmap towards improving a team's automated testing practices, loosely based on [Google's Test Certified program](https://mike-bland.com/2011/10/18/test-certified.html). ### [Principles, Practices and Idioms](pages/principles-practices-idioms.md) Fundamental automated testing and design concepts that inform the craft of writing automated tests and testable code. ### [APIs and Legacy Systems](pages/apis-and-legacy-systems.md) Technical impediments to the automated testing of existing systems and how to overcome them. ### [Rapid Prototyping](pages/rapid-prototyping.md) When it's OK to get by without writing automated tests, and when it's time to switch gears and add them. ### [Education and Advocacy](pages/education-and-advocacy.md) Models and strategies for driving adoption of automated testing throughout a development culture. ### Generating the site/hosting locally You will need [Ruby](https://www.ruby-lang.org) ( > version 2.1.5 ). You may also consider using a Ruby version manager such as [rbenv](https://github.com/sstephenson/rbenv) to help ensure that Ruby version upgrades don't mean all your [gems](https://rubygems.org/) will need to be rebuilt. To run your own local instance: ``` $ git clone [email protected]:18F/automated-testing-playbook.git $ cd automated-testing-playbook $ ./go init $ ./go serve ``` This will check that your Ruby version is supported, install the [Bundler gem](http://bundler.io/) if it is not yet installed, install all the gems needed by the playbook, and launch a running instance on `http://localhost:4000/automated-testing-playbook/`. After going through these steps, run `./go` to see a list of available commands. The `serve` command is the most common for routine development. ### Contributing 1. Fork the repo ( https://github.com/18F/automated-testing-playbook/fork ) 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create a new Pull Request Feel free to ping [@mbland](https://github.com/mbland) with any questions you may have, especially if the current documentation should've addressed your needs, but didn't. ### Public domain This project is in the worldwide [public domain](LICENSE.md). As stated in [CONTRIBUTING](CONTRIBUTING.md): > This project is in the public domain within the United States, and copyright > and related rights in the work worldwide are waived through the [CC0 1.0 > Universal public domain > dedication](https://creativecommons.org/publicdomain/zero/1.0/). > > All contributions to this project will be released under the CC0 dedication. > By submitting a pull request, you are agreeing to comply with this waiver of > copyright interest. ", Assign "at most 3 tags" to the expected json: {"id":"13076","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"