Rayrun
BlogAsk AIToolsVideosQA WikiDiscord

Continuous Integration

Continuous integration (CI) is a software development practice where developers integrate their code into a shared repository frequently, usually several times a day. Each integration is verified by an automated build and automated tests. This process helps to detect and resolve integration errors early in the development cycle, which reduces the risk of bugs and improves software quality. Continuous integration is often used in conjunction with other practices such as continuous delivery and continuous deployment.

Posts

No posts

Videos

Playwright Tutorial: Output Console logs as step traces to UI watch Mode & Traceviewer
Browser AutomationCode GenerationContinuous IntegrationCypressDeveloper Experience
Playwright Tutorial: Output Console logs as step traces to UI watch Mode & Traceviewer
Playwright Capture Screenshots and Record Videos after test execution
Continuous IntegrationPlaywright
Playwright Capture Screenshots and Record Videos after test execution
Setup & Re-Use Authentication with Playwright Dependencies!
Browser AutomationCode GenerationContinuous IntegrationTutorialTest Debugging
Setup & Re-Use Authentication with Playwright Dependencies!
How to Code a Test Automation on Youtube | Playwright JS
Browser AutomationCode GenerationContinuous IntegrationCross-Browser TestingOrganization
How to Code a Test Automation on Youtube | Playwright JS
Create feature, steps & config | Playwright & Cucumber - Typescript | Part 1
Browser AutomationCode GenerationComponent TestingContinuous IntegrationCross-Browser Testing
Create feature, steps & config | Playwright & Cucumber - Typescript | Part 1
Circle CI & GitHub Actions environment variables | Playwright Tutorial - Part 90
Continuous IntegrationTutorial
Circle CI & GitHub Actions environment variables | Playwright Tutorial - Part 90
Playwright - Set timeout, parallelisation and retries directly in your test files
Browser AutomationCode GenerationContinuous IntegrationCross-Browser TestingOrganization
Playwright - Set timeout, parallelisation and retries directly in your test files
Playwright & Lighthouse Integration | Playwright Tutorial - Part 88
AccessibilityBrowser AutomationContinuous DeploymentContinuous IntegrationCross-Browser Testing
Playwright & Lighthouse Integration | Playwright Tutorial - Part 88
Playwright with Java or Node (JavaScript / TypeScript) which is best?
Browser AutomationCode GenerationContinuous IntegrationCross-Browser TestingTypeScript
Playwright with Java or Node (JavaScript / TypeScript) which is best?
Playwright & Circle CI Integration | Playwright Tutorial - Part 85
Continuous IntegrationTutorialPlaywright
Playwright & Circle CI Integration | Playwright Tutorial - Part 85
Working with multiple elements in Playwright Test (NodeJS)
Browser AutomationCode GenerationComponent TestingContinuous IntegrationCypress
Working with multiple elements in Playwright Test (NodeJS)
How to Install Playwright Test
Browser AutomationContinuous IntegrationEnd-to-End TestingOrganizationTutorial
How to Install Playwright Test
Maximize Window | Playwright Tutorial - Part 72
Browser AutomationCode GenerationContinuous IntegrationCross-Browser TestingTutorial
Maximize Window | Playwright Tutorial - Part 72
Playwright Github Action | Playwright - part 30
Continuous IntegrationTutorialPlaywright
Playwright Github Action | Playwright - part 30

Questions

Discord Threads

BlogAsk AIToolsVideosQA WikiDiscord
TwitterGitHubLinkedIn
AboutQuestionsDiscord ForumBrowser ExtensionTagsQA Jobs

Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email luc@ray.run.