- Beginning
- build-tools
- Plugin abstract class
- Plugin aspects
- ActionPlugin
- AnalysisPlugin
- etc...
- Doing REST
- RestHandler interface
hosuaby
/ signature.commands.ts
Created
December 3, 2021 20:34
Draw signature on signature_pad (canvas) in Cypress tests
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import {random} from 'lodash-es'; | |
| /** | |
| * This is a command to draw a random signature on the canvas of signature_pad | |
| * (https://github.com/szimek/signature_pad) during Cypress tests. | |
| * | |
| * Put the present into `<project root>/cypress/support/commands/signature.commands.ts`. | |
| * Add `import './commands/signature.commands';` in `<project root>/cypress/support/index.ts`. | |
| * | |
| * After, you will be able to draw random signatures with: |
hosuaby
/ cypress-partial.js
Created
December 3, 2021 20:14
Primitive load-balancer to run Cypress specs in parallel on CI without recording
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** | |
| * Primitive load-balancer to split Cypress specs across multiple runners. This script assumes that | |
| * all your specs are in the folder '<project root>/cypress/integration'. It uses the number of | |
| * tests per spec file as sole criteria to split specs between runners. | |
| * | |
| * This script accepts two arguments: the total number of runners and the index (starting from 0) of | |
| * the current runner. Example: | |
| * $ node cypress-partial.js 5 2 | |
| * This command asks for specs to give to the third runner of five runners. | |
| * The output of the script is a coma-separated list of specs that can be given to Cypress. Example: |
hosuaby
/ how_to_write_es_plugin.md
Last active
January 17, 2020 15:51
How to write Elasticsearch plugins
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| pattern_replace removeNonWordExceptComa [[^\p{IsAlphabetic}]&&\D&&[^,]&&\S] -> "" | |
| pattern_replace pseudoElisionHack65Synonyms { | |
| pattern (\b[a-zA-Z]\') | |
| replacement "" | |
| } | |
| index a2_onecarrefour_instore_20200108_143341 { | |
| type product |
hosuaby
/ liste_montagne.md
Last active
August 4, 2019 15:27
hosuaby
/ web_ui_elements_naming_convention.md
Last active
October 3, 2022 06:58
Simple convention for naming GUI elements of Web applications
Ids or names of elements (primitives or complexes) must be written in Camel Case and must to be as short as possible. All id or name must to start with one of the defined element type prefixes.
All element ids or names must use Hungarian notation to incorporate the type of element. Prefixes are used to indicate the semantic type of the element, rather than it's underlining implementation. It means that the element of GUI with button look & feel must prefixed as btn, regardless of how it is implemented, with tag <button> or with tag <a>.
Prefixes are lowercase strings of 2, 3 or 4 characters. Here a complete list of authorised prefixes:
- btn - the button or a link with a button look & feel