...you use Rubocop or Capybara. These gems most often live in your development and/or test group of the Gemfile and require English for you. Therefore to ensure that the library...
...controllers' #index actions. This way, when a change introduces an n+1 query, your test suite will blow up. Example A typical #index action looks like this. class CardsController < ApplicationController...
...systemd-networkd man file-hierarchy Übungen Erstelle dir eine Anwendung für einen Service Für Testzwecke brauchst du eine einfache App die du später als Service starten kannst. Du kannst dir...
...mit ./badapp starten. Die Anwendung startet einen Webserver. Mit curl localhost:8080 kannst du testen ob es funktioniert. Erstelle einen systemd Service der badapp startet. Wenn die App erfolgreich startet...
...Groups so, dass von deinen EC2 Instanzen in der ASG darauf zugegriffen werden kann. Teste die Verbindung manuell. Entferne die asg_instance_types und ersetze sie durch eine variable, die...
SMTP validation: connects to the host received from DNS and starts a test delivery to find out if the recipient mailbox actually exists tl;dr: We suggest you...
...introduced rules. You can use them in your .gitlab-ci.yml in your project. To limit test runs to merge requests and the master branch, you can write this: tests: script: bundle...
...exec rake tests rules: - if: '$CI_COMMIT_BRANCH == "master"' - if: '$CI_PIPELINE_SOURCE == "merge_request_event...
Geordi can also be configured to automatically update chromedriver each time you run tests. For that, edit the global configuration file ~/.config/geordi/global.yml and add the line auto_update_chromedriver...
...that behave differently (like mobile vs desktop navigation menus). Since you want your integration tests to behave consistently, you want to set a specific size for your tests' browser windows...
...simply switch the driver via Capybara.current_driver = :selenium. If you use Cucumber for integration testing, wrap that into something like Before('@javascript') {...
Benefits of using device metrics are:
...use feature detection or a polyfill when using this API, to avoid unforeseen results. // Test via a getter in the options object to see if the passive property is accessed...
...var supportsPassive = false; try { var opts = Object.defineProperty({}, 'passive', { get: function() { supportsPassive = true; } }); window.addEventListener("testPassive", null, opts); window.removeEventListener("testPassive", null, opts); } catch (e) {} // Use our detect's results. passive applied if...
When you load a with a nonce, that script can await import() additional sources from any hostname. The nonce is propagated automatically for the one purpose of importing more scripts. This is not related to strict-dynamic, which propagates nonces for any propose not limited to imports (e.g. inserting elements). Example We have a restrictive CSP that only allows nonces: Content-Security-Policy: default-src 'none'; script-src 'nonce-secret123' Our HTML loads script.js using that nonce: Our script.js imports other.js without a nonce: let other = await import('other.js') console.log("Look, script.js has imported %o", other) The import succeeds without a nonce, due to implicit nonce propagation. Why this is useful In modern build pipelines, code splitting (chunking) is implemented using dynamic imports. Nonce propagation allows us to use automatic chunking with restrictive, nonce-based CSPs without using strict-dynamic. E.g. esbuild automatically groups dynamically imported modules into chunks, and writes that chunk to disk. The compiled build has an await import('assets/chunk-NAXSMFJV.js'). There's no way to inject a nonce into that import(), but implicit nonce propagation still allows the request. Should I worry about this? It would require some truly strange code for user input to make it into an import() argument. I wouldn't lose sleep over this. Is this a browser bug? It is by design. Here are some sources: HTML Spec Section 8 (Web Application APIs) (search for "descendant script fetch options") Chromium test ensuring none propagation Firefox bug implementing nonce propagation CSP issue: Someone concerned about propagation being a vulnerability CSP issue: Proposal for import-src that went nowhere Are other CSP sources also propagated? No, only nonces. In particular host-based CSPs do not propagate trust. For example, you only allow scripts from our own host (no nonces): Content-Security-Policy: default-src 'none'; script-src 'self' Our HTML loads script.js from our own host: Our script.js imports other.js from a different host: let other = await import('https://other-host.com/other.js') This fails with a CSP violation: Executing inline script violates the following Content Security Policy directive 'script-src 'self''
If you need a sample video with certain properties for a test you can create one using ffmpeg. You might want a very low bitrate file to speed up processing...
...in your test. (e.g. you only care about the length, then you can create a video with a very low resolution and framerate) Create a 21s video with 1fps and...
...because capybara is a dependency of cucumber-rails), which will break all your tests. The fix Bundler >= 1.14 has a --conservative flag. Using the conservative flag allows bundle update GEM...
...EC2 Instanzen zugewiesen werden. Anschließend verbindest du dich per SSM auf deine Instanzen und testest den S3 Zugriff mit der aws-cli. Deprovisioniere deine Infrastruktur mit terraform destroy...
Das Backup sollte komprimiert sein Lösche Backups älter als 30 Tage (zum Testen kannst du kürzere Zeiträume wählen) Das Backup soll mit einem Cronjob ausgeführt werden. Immer wenn...
In our monitoring, RabbitMQ queues like aliveness-test may show up as unresponsive, with a ping timeout after 10 seconds. The logfile will generally read like this: operation queue.delete caused...
...to perform operation on queue 'example' in vhost '/' due to timeout For the aliveness-test queue, you can can use this command to delete it: rabbitmqctl eval 'rabbit_amqqueue:internal...
This is my configuration: # ~/.claude/notify.sh # Note: You need to `chmod +x` this #!/bin/bash # Test usage: # echo '{ "title": "foo", "message": "bar" }' | bash ~/.claude/notify.sh EDITOR_COMMAND="/snap/bin/rubymine" INPUT=$(cat)
...Setup job that will only run for Rails environment "staging" end end You may test the cron output like this (no changes will be made to your crontab):
...task that will only run for Capistrano stage "customer1-staging" end end You may test the cron output like this (no changes will be made to your crontab): STAGE=customer1...
...I use git worktree? You can use more than one working tree to ... ... run tests while working on another branch ... compare multiple versions ... work on a different branch without disturbing...
...up DOM elements. There are also matchers like have_field to make expectations during tests. These methods also have a number of options to influence the lookup. E.g. the :disabled...
...Just increase the last index when proceeding to the next example. Handy when the test file frequently changes, e.g. because before blocks are modified. The line number approach would easily...
...it only cares about the HTML-Tag type. Example. This might lead to breaking tests when your html changes. Once browser support is fulfilled prefiltering nth-child selector will be...
We are using Spring in our tests for sequential test execution but not for parallel test execution. And Rails requires you to set the config.cache_classes = false if you are...
...using Spring in tests. With our setup, this would raise the following error in cucumber-rails for parallel test executions due to some legacy database cleaner issue. WARNING: You have...
...callback passed to promiseState will be called asynchronously in the next microtask. Usage example: Tests Note Since this card was written Jasmine has implemented asynchronous matchers that let you expect...
...sufficient to use the then() function. Where promiseState() becomes useful is when writing unit tests for a function that returns a promise. Let's say we write a promise-based...
...For each chapter: You should do all the programming exercises. You can skip the testing exercises. We are going to learn testing in a later card. We're also using...
...different testing frameworks and different types of tests than the tutorial. We will also be using a different development environment than the book suggests. Deviate from the following instructions: