This is a bash script, as an example, on how to do click-testing GUI based on finding components based on how they look.
- opencv
- scrot
- findimage
- xdotool
| #include <time.h> // Robert Nystrom | |
| #include <stdio.h> // @munificentbob | |
| #include <stdlib.h> // for Ginny | |
| #define r return // 2008-2019 | |
| #define l(a, b, c, d) for (i y=a;y\ | |
| <b; y++) for (int x = c; x < d; x++) | |
| typedef int i;const i H=40;const i W | |
| =80;i m[40][80];i g(i x){r rand()%x; | |
| }void cave(i s){i w=g(10)+5;i h=g(6) | |
| +3;i t=g(W-w-2)+1;i u=g(H-h-2)+1;l(u |
| import produce from 'immer'; | |
| import {createStore} from 'redux'; | |
| const handleActions = (actionsMap, defaultState) => ( | |
| state = defaultState, | |
| {type, payload} | |
| ) => | |
| produce(state, draft => { | |
| const action = actionsMap[type]; | |
| action && action(draft, payload); |
| export default (fileInfo, api) => { | |
| const j = api.jscodeshift; | |
| const methods = []; | |
| const root = j(fileInfo.source); | |
| const body = root.find(j.Program).get('body', 0).node; | |
| const { comments } = body; | |
| delete body.comments | |
| root.get().node.comments = comments; | |
| // Trie.js - super simple JS implementation | |
| // https://en.wikipedia.org/wiki/Trie | |
| // ----------------------------------------- | |
| // we start with the TrieNode | |
| function TrieNode(key) { | |
| // the "key" value will be the character in sequence | |
| this.key = key; | |
| # You will need fswatch installed (available in homebrew and friends) | |
| # The command below will run tests and wait until fswatch writes something. | |
| # The --stale flag will only run stale entries, it requires Elixir v1.3. | |
| fswatch lib/ test/ | mix test --stale --listen-on-stdin |
This is a bash script, as an example, on how to do click-testing GUI based on finding components based on how they look.
By the end of this quick guide, you will know how to compile a Phoenix app release using Exrm and run it inside a Docker container. I've found only a couple of articles that discuss getting an Elixir app up and running inside a Docker container, and even those only touched on some parts of the process. The idea is that this guide will give you a full end-to-end example of how to get all the pieces and parts working together so that you are able to deploy your Phoenix application inside a Docker container.
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| #!/usr/bin/env python3 | |
| import sys | |
| import os | |
| def curl_to_ab(curl_cmd: list, num: int=200, cur: int=4) -> str: | |
| """ | |
| Translate a cURL command created by Chrome's developer tools into a | |
| command for ``ab``, the ApacheBench HTTP benchmarking tool. |
| /* | |
| This script attempts to identify all CSS classes mentioned in HTML but not defined in the stylesheets. | |
| In order to use it, just run it in the DevTools console (or add it to DevTools Snippets and run it from there). | |
| Note that this script requires browser to support `fetch` and some ES6 features (fat arrow, Promises, Array.from, Set). You can transpile it to ES5 here: https://babeljs.io/repl/ . | |
| Known limitations: | |
| - it won't be able to take into account some external stylesheets (if CORS isn't set up) | |
| - it will produce false negatives for classes that are mentioned in the comments. |