Leave end-to-end testing to Capybara
Download as key, pdf4 likes2,325 views
Leave end-to-end testing to Capybara. Capybara is a web testing tool that simulates user interactions with a website. It allows automating browser interactions for scenarios and features using domain-specific languages like Cucumber. Capybara supports using different drivers like Selenium for JavaScript interactions and HtmlUnit for non-JavaScript sites. Specifying the driver and JavaScript support in tests allows running tests across different environments.
1 of 53
Downloaded 44 times
![DSL
feature ' ' do
background do
setup_tdiary
end
scenario ' ' do
visit '/'
within('title') do
page.should have_content(' ') }
end
within('h1') do
page.should have_content(' ')
end
page.should have_css('a[href="update.rb"]')
end
end](https://image.slidesharecdn.com/oedorubykaigi01-110410090842-phpapp02/85/Leave-end-to-end-testing-to-Capybara-27-320.jpg)
Recommended
The details of CI/CD environment for Ruby
The details of CI/CD environment for RubyHiroshi SHIBATA The document discusses the strategy for building and testing the programming language Hiroshi. It covers:
1. The Ruby Core team which maintains the language and includes over 80 volunteers.
2. The testing strategy for Ruby which involves testing at different levels from the interpreter to libraries. Extensive tests are run on Linux, Windows and macOS.
3. The CI environments used for Ruby development including GitHub Actions, Travis CI and AppVeyor, as well as internal VM clusters. Test results are collected on Ruby CI and discussed on Slack.
Gate of Agile Web Development
Gate of Agile Web DevelopmentKoichi ITO The document discusses a computer programmer who is also a guitarist and leads an Agile software development team. It includes code snippets from programming languages like Ruby. There are also descriptions of using source control tools like Git for managing branches, tags, and cherry-picking commits.
How to develop Jenkins plugin using to ruby and Jenkins.rb
How to develop Jenkins plugin using to ruby and Jenkins.rbHiroshi SHIBATA - The document discusses developing Jenkins plugins using Ruby and the jpi tool. It covers generating a sample wrapper plugin, configuring the plugin, and building and releasing the plugin through jpi commands.
- The speaker demonstrates creating a sample "rbenv" plugin with jpi to configure Ruby versions and gems for builds.
- Commands like jpi new, generate, build, server and release are used to generate the plugin scaffolding, configure the wrapper, build the plugin file, host it locally for testing, and prepare it for release.
20141210 rakuten techtalk
20141210 rakuten techtalkHiroshi SHIBATA This document discusses how to change an organization and provides examples of how the author's company changed their technical organization and processes. Some of the key points discussed include adopting agile methodologies like Scrum, emphasizing testing and use of open source tools, upgrading technologies and adopting newer versions of Ruby and Rails, and optimizing teams and processes to better support the business.
20140626 red dotrubyconf2014
20140626 red dotrubyconf2014Hiroshi SHIBATA 1) The Ruby programming language is now primarily developed and maintained by the open source community rather than just Matz, its original creator.
2) To contribute to Ruby, developers should submit bug reports with a minimum reproducible case and logs from different Ruby versions, or submit feature requests with use cases and naming conventions.
3) While GitHub is commonly used, some core developers prefer Redmine, which is where Matz primarily focuses and requires tickets to be submitted.
20140925 rails pacific
20140925 rails pacificHiroshi SHIBATA This document discusses how to craft a Rails culture within a company by enforcing modern architectures, open source practices, and integrating administrative functions. It provides examples of migrating from older Ruby and Rails versions, replacing legacy middleware, and designing internal or separate apps for administrative tasks. The document advocates an evolutionary approach of learning Rails step-by-step and establishing practices like GitHub workflow and ChatOps to support DevOps.
20140425 ruby conftaiwan2014
20140425 ruby conftaiwan2014Hiroshi SHIBATA The document discusses migrating from a legacy Ruby on Rails application to a newer version of Rails. It provides examples of performance improvements when upgrading Ruby from 1.8.6 to 2.1.1 and Rails from 2.0 to 4.1. It also discusses strategies for migrating codebases while maintaining zero downtime deployments.
20140419 oedo rubykaigi04
20140419 oedo rubykaigi04Hiroshi SHIBATA This document summarizes the key points in migrating a legacy Rails 2.0 application to a newer version of Rails. It discusses upgrading to Rails 2.3 first to address compatibility issues. Then it recommends upgrading to Ruby 2.1 and Rails 4.1 to get performance improvements from the language and framework updates. Various techniques are presented for the migration process such as running the newer versions in production gradually.
20140918 ruby kaigi2014
20140918 ruby kaigi2014Hiroshi SHIBATA This document discusses various topics related to developing Ruby, including Ruby core policy and development process. It provides guidance on how to properly submit issues and pull requests to the Ruby core team, such as using Redmine for reporting issues rather than Twitter or blogs, and providing a clear use case and sample code. It also outlines the Ruby release planning process.
How DSL works on Ruby
How DSL works on RubyHiroshi SHIBATA This document summarizes a presentation about the future of the Rake gem and domain-specific languages (DSLs) in Ruby.
The presentation discusses:
1. How Rake works as a Make-like program implemented in Ruby syntax with tasks and dependencies. Rake files use standard Ruby syntax.
2. Examples of common patterns for building internal DSLs in Ruby using class/module methods, method definition, implicit/explicit code blocks, and instance evaluation.
3. How popular Ruby gems like Rake, Bundler, and Thor use DSL techniques and inherit from each other to provide domain-specific interfaces.
mruby で mackerel のプラグインを作るはなし
mruby で mackerel のプラグインを作るはなしHiroshi SHIBATA This document discusses how to create Mackerel plugins using mruby. It explains what Mackerel plugins are, the required format, and how to write command line tools and classes in mruby. It then provides an example of implementing Redis commands like SCARD and SMEMBERS in mruby-redis by reading the C source and making additions. This allows monitoring Redis set data with Mackerel. Finally, it shows a sample Mackerel plugin for monitoring Sidekiq job counts.
How to Begin Developing Ruby Core
How to Begin Developing Ruby CoreHiroshi SHIBATA This document provides an introduction to testing the Ruby programming language. It discusses how to set up a development environment to run Ruby's core tests, describes the various test suites and tasks, and provides examples of test files. The document encourages contributors to test Ruby by cloning its repository, running the test suites locally, focusing tests in specific areas, and submitting patches for new or updated tests.
How to test code with mruby
How to test code with mrubyHiroshi SHIBATA This document discusses testing code written for mruby, a lightweight Ruby implementation. It proposes using the mruby runtime itself to test code, rather than Ruby, by using the mruby-mtest library. This allows testing mruby code directly using the same binaries and libraries as production. Sample code shows how to structure tests and set up a test runner to execute tests against the mruby binary. Testing code with mruby provides faster, more direct testing compared to using Ruby.
tDiary annual report 2009 - Sapporo Ruby Kaigi02
tDiary annual report 2009 - Sapporo Ruby Kaigi02Hiroshi SHIBATA This document is the annual report for 2009 of tDiary, an open-source web diary application built using Ruby. It discusses updates made to tDiary in 2009, including releasing version 2.3.2 which added compatibility with Ruby 1.9, as well as plans for future versions including adopting testing frameworks like RSpec and Cucumber, migrating to use the Rack middleware interface, and adding support for XML-RPC and Atom/PubSubHubbub. It also promotes involvement with the tDiary project on GitHub and in the Japanese Ruby community.
Gems on Ruby
Gems on RubyHiroshi SHIBATA 1. The document discusses RubyGems, Bundler, and rbenv/ruby-build. It provides an overview of each tool's purpose and history.
2. RubyGems is the package manager for Ruby libraries. Bundler is a tool for managing dependencies of Ruby applications. Rbenv/ruby-build allow managing multiple Ruby versions and building Ruby.
3. The document outlines plans to further integrate RubyGems and Bundler, but notes Bundler 2 has not yet been released, which is needed for full integration. Security improvements have also been made to RubyGems.
Practical ngx_mruby
Practical ngx_mrubyHiroshi SHIBATA This document provides an overview and examples of using ngx_mruby, which allows embedding the mruby scripting language in the nginx web server. It introduces ngx_mruby and how it works, provides instructions for building and installing ngx_mruby, and gives several code examples for common tasks like content handling, logging, redirection, and authorization using ngx_mruby. Key features covered include accessing nginx variables and requests, sharing data across request phases and worker processes, and integrating mruby gems.
Middleware as Code with mruby
Middleware as Code with mrubyHiroshi SHIBATA This document discusses using the mruby programming language as middleware code. Some key points:
- mruby allows embedding Ruby code into middleware applications like web servers. This provides a powerful programming environment for Rubyists to write middleware code.
- ngx_mruby is an example of using mruby with the nginx web server. It allows placing Ruby code handlers and variables in the nginx configuration file.
- Advantages of mruby include producing a single binary without separate Ruby files, and ability to embed Ruby runtime and code directly into middleware applications like web servers.
- The document demonstrates sample ngx_mruby code for content handlers, variables, and initialization/worker scripts. It
Gemification plan of Standard Library on Ruby
Gemification plan of Standard Library on RubyHiroshi SHIBATA The document discusses plans to extract standard Ruby libraries into gems to improve maintenance. It notes libraries have been extracted as default or bundled gems, with different maintenance policies. Benefits include easier bugfixes and new features, but concerns include complex dependencies, need for cross-platform support, and ensuring gems do not conflict with standard libraries. It provides statistics on libraries extracted in Ruby 2.4 and 2.5 and discusses ongoing work like OpenSSL extraction and addressing naming conflicts.
RubyGems 3 & 4
RubyGems 3 & 4Hiroshi SHIBATA The document discusses changes and new features in RubyGems 3 and 4, the package manager for the Ruby programming language. Some key points:
- RubyGems 3 removes deprecated methods and support for older Ruby versions. It adds warnings for deprecated methods and allows direct use of the release toolchain.
- RubyGems 4 will have incompatible changes like upgrading the dependency resolver, making conservative installation the default, changing the behavior of default installation, and making user installation the default.
- Other topics discussed include deprecation handling, code search tools for RubyGems code, testing changes on all Ruby versions, removing deprecated code, and pre-releasing RubyGems updates.
How to develop the Standard Libraries of Ruby?
How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA I maintain the RubyGems, Bundler and the standard libraries of the Ruby language. So, I've been extract many of the standard libraries to default gems and GitHub at Ruby 3.0. But the some of libraries still remains in only Ruby repository. I will describe these situation.
Middleware as Code with mruby
Middleware as Code with mrubyHiroshi SHIBATA The document discusses testing Ruby code used in ngx_mruby, an open source project that embeds the mruby scripting language into the nginx web server. It proposes a testing approach using a dummy implementation of the ngx_mruby API to test the Ruby code in isolation without needing nginx. Sample code shows how to set up dummy request and connection classes to mimic the ngx_mruby environment, as well as a memcached class to test code that interacts with memcached. A skeleton test case demonstrates how to write tests using this approach with the Test::Unit framework to test specific behaviors like restricting requests based on cookie sessions.
An introduction and future of Ruby coverage library
An introduction and future of Ruby coverage librarymametter Ruby's current test coverage feature, coverage.so, only measures line coverage. The speaker proposes expanding it to support function and branch coverage in Ruby 2.5. This would involve updating the coverage.so API to return additional coverage data types and structure the output data in a more extensible way. A preliminary demo applying the new coverage.so to Ruby code showed it can integrate with C code coverage from GCOV and display results in LCOV format. The speaker seeks feedback on the proposed API design to finalize it for Ruby 2.5.
How to distribute Ruby to the world
How to distribute Ruby to the worldHiroshi SHIBATA The document discusses how the Ruby programming language is developed and released. It describes the Ruby core team and committers, release cycles, backporting fixes, testing on various platforms via Ruby CI, packaging and distributing releases, handling security issues, and the *.ruby-lang.org domains. It also discusses moving the source code repository from Subversion to Git and migrating development tools and processes.
The Future of Dependency Management for Ruby
The Future of Dependency Management for RubyHiroshi SHIBATA The document discusses integrating the Bundler dependency manager into the Ruby programming language core. It covers the benefits of integrating Bundler, such as allowing developers to manage library dependencies directly within Ruby projects. It also discusses challenges faced in integrating Bundler, like ensuring Bundler test suites work properly within the Ruby core codebase. The author details steps taken to start merging Bundler code into Ruby, including adding a "make test-bundler" command to run Bundler tests during development.
The Future of Bundled Bundler
The Future of Bundled BundlerHiroshi SHIBATA 1. The first step of package management integration discusses integrating Bundler into RubyGems to provide bundled gems as the default package management solution.
2. What's happened in Ruby 2.6 discusses updates to RubyGems 3 and Bundler 2 that dropped support for older Ruby versions and integrated Bundler fully into Ruby 2.6 as the default package manager.
3. BugMash after releasing Ruby 2.6 summarizes issues that came up after Ruby 2.6's release regarding path injection problems with LOAD_PATH, invalid gemspec generation by the installer, and Bundler version switching on Heroku.
The Future of library dependency management of Ruby
The Future of library dependency management of RubyHiroshi SHIBATA The document discusses the integration of package management in Ruby. It provides an overview of RubyGems and Bundler, the two main tools for managing library dependencies in Ruby. It also outlines the roadmap for further integrating RubyGems and Bundler, including merging RubyGems 3.2 into Ruby 2.8 and moving Bundler's canonical repository to RubyGems.org. Additionally, it discusses challenges around dependency resolution compatibility and activation of default gems between different versions of RubyGems and Bundler.
Gemification for Ruby 2.5/3.0
Gemification for Ruby 2.5/3.0Hiroshi SHIBATA Future of Ruby standard libraries will focus on gemification. Standard libraries will be extracted out of the Ruby core repository and maintained as default gems or bundled gems in GitHub repositories. This allows libraries to be updated independently of Ruby releases and more easily accept contributions. While this approach has benefits, it also has challenges around maintaining compatibility and complex dependencies. The process of gemification will be gradual to reduce the size of changes.
Performance Optimization of Rails Applications
Performance Optimization of Rails ApplicationsSerge Smetana The document discusses optimizing the performance of Ruby on Rails applications. It covers optimizing Ruby code, Rails code, database queries, using alternative Ruby implementations like JRuby, and optimizing for production environments including shared filesystems, load balancing, and the frontend. Specific optimizations discussed include rewriting parts of the Date class in C, template inlining in Rails, pushing SQL conditions into subqueries, and using memcached instead of filesystem caching on a shared network.
Capybara and cucumber with DSL using ruby
Capybara and cucumber with DSL using rubyDeepak Chandella This presentation covers detailed overview of capybara and cucumber with DSL using ruby language. it covers below aspects.
- Setup for capybara and cucumber
- Overview and directory structure.
- Capybara using cucumber or any other ruby test framework.
Setting up the driver.
- The DSL (Navigation, clicking link or button, interacting with forms)
- The DSL (querying, finding, scoping)
- The DSL (windows, scripting, modals, debugging)
- Capybara test execution, tagging, reporting.
Capybara
CapybaraMona Soni Capybara is a tool for integration testing Ruby web applications that allows automating browser interactions directly from tests. It is driver agnostic and supports RackTest, Selenium, Capybara-webkit, and other drivers, and provides a DSL for writing tests that simulate user interactions like clicks, fills, and matches against page content. Capybara tests can be written using Cucumber or RSpec and configured to run quickly using headless drivers or remotely on servers.
More Related Content
What's hot (20)
20140918 ruby kaigi2014
20140918 ruby kaigi2014Hiroshi SHIBATA This document discusses various topics related to developing Ruby, including Ruby core policy and development process. It provides guidance on how to properly submit issues and pull requests to the Ruby core team, such as using Redmine for reporting issues rather than Twitter or blogs, and providing a clear use case and sample code. It also outlines the Ruby release planning process.
How DSL works on Ruby
How DSL works on RubyHiroshi SHIBATA This document summarizes a presentation about the future of the Rake gem and domain-specific languages (DSLs) in Ruby.
The presentation discusses:
1. How Rake works as a Make-like program implemented in Ruby syntax with tasks and dependencies. Rake files use standard Ruby syntax.
2. Examples of common patterns for building internal DSLs in Ruby using class/module methods, method definition, implicit/explicit code blocks, and instance evaluation.
3. How popular Ruby gems like Rake, Bundler, and Thor use DSL techniques and inherit from each other to provide domain-specific interfaces.
mruby で mackerel のプラグインを作るはなし
mruby で mackerel のプラグインを作るはなしHiroshi SHIBATA This document discusses how to create Mackerel plugins using mruby. It explains what Mackerel plugins are, the required format, and how to write command line tools and classes in mruby. It then provides an example of implementing Redis commands like SCARD and SMEMBERS in mruby-redis by reading the C source and making additions. This allows monitoring Redis set data with Mackerel. Finally, it shows a sample Mackerel plugin for monitoring Sidekiq job counts.
How to Begin Developing Ruby Core
How to Begin Developing Ruby CoreHiroshi SHIBATA This document provides an introduction to testing the Ruby programming language. It discusses how to set up a development environment to run Ruby's core tests, describes the various test suites and tasks, and provides examples of test files. The document encourages contributors to test Ruby by cloning its repository, running the test suites locally, focusing tests in specific areas, and submitting patches for new or updated tests.
How to test code with mruby
How to test code with mrubyHiroshi SHIBATA This document discusses testing code written for mruby, a lightweight Ruby implementation. It proposes using the mruby runtime itself to test code, rather than Ruby, by using the mruby-mtest library. This allows testing mruby code directly using the same binaries and libraries as production. Sample code shows how to structure tests and set up a test runner to execute tests against the mruby binary. Testing code with mruby provides faster, more direct testing compared to using Ruby.
tDiary annual report 2009 - Sapporo Ruby Kaigi02
tDiary annual report 2009 - Sapporo Ruby Kaigi02Hiroshi SHIBATA This document is the annual report for 2009 of tDiary, an open-source web diary application built using Ruby. It discusses updates made to tDiary in 2009, including releasing version 2.3.2 which added compatibility with Ruby 1.9, as well as plans for future versions including adopting testing frameworks like RSpec and Cucumber, migrating to use the Rack middleware interface, and adding support for XML-RPC and Atom/PubSubHubbub. It also promotes involvement with the tDiary project on GitHub and in the Japanese Ruby community.
Gems on Ruby
Gems on RubyHiroshi SHIBATA 1. The document discusses RubyGems, Bundler, and rbenv/ruby-build. It provides an overview of each tool's purpose and history.
2. RubyGems is the package manager for Ruby libraries. Bundler is a tool for managing dependencies of Ruby applications. Rbenv/ruby-build allow managing multiple Ruby versions and building Ruby.
3. The document outlines plans to further integrate RubyGems and Bundler, but notes Bundler 2 has not yet been released, which is needed for full integration. Security improvements have also been made to RubyGems.
Practical ngx_mruby
Practical ngx_mrubyHiroshi SHIBATA This document provides an overview and examples of using ngx_mruby, which allows embedding the mruby scripting language in the nginx web server. It introduces ngx_mruby and how it works, provides instructions for building and installing ngx_mruby, and gives several code examples for common tasks like content handling, logging, redirection, and authorization using ngx_mruby. Key features covered include accessing nginx variables and requests, sharing data across request phases and worker processes, and integrating mruby gems.
Middleware as Code with mruby
Middleware as Code with mrubyHiroshi SHIBATA This document discusses using the mruby programming language as middleware code. Some key points:
- mruby allows embedding Ruby code into middleware applications like web servers. This provides a powerful programming environment for Rubyists to write middleware code.
- ngx_mruby is an example of using mruby with the nginx web server. It allows placing Ruby code handlers and variables in the nginx configuration file.
- Advantages of mruby include producing a single binary without separate Ruby files, and ability to embed Ruby runtime and code directly into middleware applications like web servers.
- The document demonstrates sample ngx_mruby code for content handlers, variables, and initialization/worker scripts. It
Gemification plan of Standard Library on Ruby
Gemification plan of Standard Library on RubyHiroshi SHIBATA The document discusses plans to extract standard Ruby libraries into gems to improve maintenance. It notes libraries have been extracted as default or bundled gems, with different maintenance policies. Benefits include easier bugfixes and new features, but concerns include complex dependencies, need for cross-platform support, and ensuring gems do not conflict with standard libraries. It provides statistics on libraries extracted in Ruby 2.4 and 2.5 and discusses ongoing work like OpenSSL extraction and addressing naming conflicts.
RubyGems 3 & 4
RubyGems 3 & 4Hiroshi SHIBATA The document discusses changes and new features in RubyGems 3 and 4, the package manager for the Ruby programming language. Some key points:
- RubyGems 3 removes deprecated methods and support for older Ruby versions. It adds warnings for deprecated methods and allows direct use of the release toolchain.
- RubyGems 4 will have incompatible changes like upgrading the dependency resolver, making conservative installation the default, changing the behavior of default installation, and making user installation the default.
- Other topics discussed include deprecation handling, code search tools for RubyGems code, testing changes on all Ruby versions, removing deprecated code, and pre-releasing RubyGems updates.
How to develop the Standard Libraries of Ruby?
How to develop the Standard Libraries of Ruby?Hiroshi SHIBATA I maintain the RubyGems, Bundler and the standard libraries of the Ruby language. So, I've been extract many of the standard libraries to default gems and GitHub at Ruby 3.0. But the some of libraries still remains in only Ruby repository. I will describe these situation.
Middleware as Code with mruby
Middleware as Code with mrubyHiroshi SHIBATA The document discusses testing Ruby code used in ngx_mruby, an open source project that embeds the mruby scripting language into the nginx web server. It proposes a testing approach using a dummy implementation of the ngx_mruby API to test the Ruby code in isolation without needing nginx. Sample code shows how to set up dummy request and connection classes to mimic the ngx_mruby environment, as well as a memcached class to test code that interacts with memcached. A skeleton test case demonstrates how to write tests using this approach with the Test::Unit framework to test specific behaviors like restricting requests based on cookie sessions.
An introduction and future of Ruby coverage library
An introduction and future of Ruby coverage librarymametter Ruby's current test coverage feature, coverage.so, only measures line coverage. The speaker proposes expanding it to support function and branch coverage in Ruby 2.5. This would involve updating the coverage.so API to return additional coverage data types and structure the output data in a more extensible way. A preliminary demo applying the new coverage.so to Ruby code showed it can integrate with C code coverage from GCOV and display results in LCOV format. The speaker seeks feedback on the proposed API design to finalize it for Ruby 2.5.
How to distribute Ruby to the world
How to distribute Ruby to the worldHiroshi SHIBATA The document discusses how the Ruby programming language is developed and released. It describes the Ruby core team and committers, release cycles, backporting fixes, testing on various platforms via Ruby CI, packaging and distributing releases, handling security issues, and the *.ruby-lang.org domains. It also discusses moving the source code repository from Subversion to Git and migrating development tools and processes.
The Future of Dependency Management for Ruby
The Future of Dependency Management for RubyHiroshi SHIBATA The document discusses integrating the Bundler dependency manager into the Ruby programming language core. It covers the benefits of integrating Bundler, such as allowing developers to manage library dependencies directly within Ruby projects. It also discusses challenges faced in integrating Bundler, like ensuring Bundler test suites work properly within the Ruby core codebase. The author details steps taken to start merging Bundler code into Ruby, including adding a "make test-bundler" command to run Bundler tests during development.
The Future of Bundled Bundler
The Future of Bundled BundlerHiroshi SHIBATA 1. The first step of package management integration discusses integrating Bundler into RubyGems to provide bundled gems as the default package management solution.
2. What's happened in Ruby 2.6 discusses updates to RubyGems 3 and Bundler 2 that dropped support for older Ruby versions and integrated Bundler fully into Ruby 2.6 as the default package manager.
3. BugMash after releasing Ruby 2.6 summarizes issues that came up after Ruby 2.6's release regarding path injection problems with LOAD_PATH, invalid gemspec generation by the installer, and Bundler version switching on Heroku.
The Future of library dependency management of Ruby
The Future of library dependency management of RubyHiroshi SHIBATA The document discusses the integration of package management in Ruby. It provides an overview of RubyGems and Bundler, the two main tools for managing library dependencies in Ruby. It also outlines the roadmap for further integrating RubyGems and Bundler, including merging RubyGems 3.2 into Ruby 2.8 and moving Bundler's canonical repository to RubyGems.org. Additionally, it discusses challenges around dependency resolution compatibility and activation of default gems between different versions of RubyGems and Bundler.
Gemification for Ruby 2.5/3.0
Gemification for Ruby 2.5/3.0Hiroshi SHIBATA Future of Ruby standard libraries will focus on gemification. Standard libraries will be extracted out of the Ruby core repository and maintained as default gems or bundled gems in GitHub repositories. This allows libraries to be updated independently of Ruby releases and more easily accept contributions. While this approach has benefits, it also has challenges around maintaining compatibility and complex dependencies. The process of gemification will be gradual to reduce the size of changes.
Performance Optimization of Rails Applications
Performance Optimization of Rails ApplicationsSerge Smetana The document discusses optimizing the performance of Ruby on Rails applications. It covers optimizing Ruby code, Rails code, database queries, using alternative Ruby implementations like JRuby, and optimizing for production environments including shared filesystems, load balancing, and the frontend. Specific optimizations discussed include rewriting parts of the Date class in C, template inlining in Rails, pushing SQL conditions into subqueries, and using memcached instead of filesystem caching on a shared network.
Similar to Leave end-to-end testing to Capybara (18)
Capybara and cucumber with DSL using ruby
Capybara and cucumber with DSL using rubyDeepak Chandella This presentation covers detailed overview of capybara and cucumber with DSL using ruby language. it covers below aspects.
- Setup for capybara and cucumber
- Overview and directory structure.
- Capybara using cucumber or any other ruby test framework.
Setting up the driver.
- The DSL (Navigation, clicking link or button, interacting with forms)
- The DSL (querying, finding, scoping)
- The DSL (windows, scripting, modals, debugging)
- Capybara test execution, tagging, reporting.
Capybara
CapybaraMona Soni Capybara is a tool for integration testing Ruby web applications that allows automating browser interactions directly from tests. It is driver agnostic and supports RackTest, Selenium, Capybara-webkit, and other drivers, and provides a DSL for writing tests that simulate user interactions like clicks, fills, and matches against page content. Capybara tests can be written using Cucumber or RSpec and configured to run quickly using headless drivers or remotely on servers.
Capybara with Rspec
Capybara with RspecOmnia Helmi Learning how to use capybara and capybara-webkit with rspec.
Example :- https://github.com/OmniaGM/learn-capybara
Ruby onrails cucumber-rspec-capybara
Ruby onrails cucumber-rspec-capybaraBindesh Vijayan This document discusses using Cucumber and Capybara for behavior-driven development (BDD) testing in Ruby on Rails applications. It provides an overview of Cucumber for writing acceptance tests as plain text scenarios. It demonstrates defining a sample user login feature and scenario, and describes how to write step definitions using Capybara's domain-specific language to simulate user interactions like filling forms and clicking buttons.
Behavior Driven Development Testing (BDD)
Behavior Driven Development Testing (BDD)Dignitas Digital Pvt. Ltd. BDD (Behaviour Driven Development) is a synthesis and refinement of practices stemming from TDD (Test Driven Development) and ATDD (Acceptance Test Driven Development). Although BDD is principally an idea about how software development should be managed by both business interests and technical insight, the practice of BDD does assume the use of specialized software tools to support the development process.
Behavioural Testing Ruby/Rails Apps @ Scale - Rspec & Cucumber
Behavioural Testing Ruby/Rails Apps @ Scale - Rspec & CucumberUdaya Kiran This document provides an overview of behavioural testing for Ruby on Rails applications at scale using RSpec and Cucumber. It discusses unit, integration and acceptance testing. It then covers the Test Driven Development (TDD) and Behaviour Driven Development (BDD) approaches. The rest of the document explains how to implement testing with RSpec, Shoulda-Matchers, Factory Girl, Cucumber, Gherkin and Capybara. It also discusses different web drivers that can be used like Rack Test, Selenium, Capybara-webkit and Poltergeist.
BDD / cucumber /Capybara
BDD / cucumber /CapybaraShraddhaSF Behavior Driven Development (BDD) focuses on defining expected application behaviors through user stories. Cucumber and Capybara are tools that support BDD. Cucumber allows writing tests in plain language and organizing them into feature files. Capybara is a framework that simulates user interactions and uses a domain-specific language to write tests. It supports drivers like Selenium to test web applications with JavaScript.
Capybara + RSpec - ruby dsl-based web ui qa automation
Capybara + RSpec - ruby dsl-based web ui qa automationCOMAQA.BY The document discusses RSpec and Capybara, which are the most popular and stable tools for web UI automation testing in Ruby. RSpec is a BDD framework that serves as a testing and assertion tool. Capybara is a web driver wrapper that allows automating interactions like visiting pages, filling forms, and clicking elements. The document provides examples of setting up RSpec and Capybara and matching common interactions and selectors.
Cross-browser testing in the real world
Cross-browser testing in the real worldMartin Kleppmann The document discusses several frequently encountered issues when testing cross-browser, including time dependence, managing test virtual machines, random DOM IDs, testing layout, unit testing JavaScript, model layer access in tests, starting state, and parallel test runs. Some solutions proposed include using fixtures to manage database state, cleaning up the database between tests, and starting multiple browser instances in parallel to speed up test runs.
Functional testing with capybara
Functional testing with capybarakoffeinfrei Capybara is a tool for automated user interaction testing of web applications. It allows automating browser interactions like clicking links, filling forms, and making requests. It works with several test frameworks and drivers to test against different environments. It provides a domain-specific language for describing tests in a readable way and has features for navigation, interaction, querying, finding elements, debugging, and configuration. Some examples of using it include testing a font generation application and ensuring loading states display correctly. Potential issues include slowness with some drivers and handling of dialog boxes and new windows.
Integration Test Cucumber + Webrat + Selenium
Integration Test Cucumber + Webrat + Seleniumtka This document discusses integration testing with Cucumber, Webrat, and Selenium. It provides information on each tool and how they can be used together. Cucumber is used to write feature tests in a plain language format. Webrat allows interacting with pages and making assertions in Ruby. Selenium is used to drive a real browser for tests. The document includes code examples of using each tool individually and together in a Cucumber test suite.
Cucumber
CucumberBachue Zhou Cucumber is a tool that executes plain-text behavioral tests written in Gherkin and maps them to code via step definitions to automate testing; Gherkin is a business-readable language used to describe software behavior without detailing implementation; Cucumber uses Ruby and drivers like Capybara to simulate user interactions and check outcomes of the automated tests.
Cucumber_Capybara
Cucumber_CapybaraAlexander Polovinko This document discusses using Cucumber and Capybara for UI automation. It provides an overview of Cucumber for behavior-driven development using a simple domain-specific language. Capybara is described as a library that simulates user interactions to test a Ruby application. The document outlines how to set up Cucumber and Capybara with RSpec and addresses challenges like locators, asynchronous JavaScript, and handling windows. It also discusses reporting test results and executing tests on different platforms and browsers.
Quick ref capybara
Quick ref capybarafatec This document provides an overview of how to configure and use Capybara for testing web applications. It discusses using Capybara with Cucumber, RSpec, and Test::Unit. It also describes the Capybara DSL for navigating pages, interacting with elements, making assertions, and more. Finally, it covers additional features like JavaScript support, custom selectors, and registering custom drivers.
Integration and Acceptance Testing
Integration and Acceptance TestingAlan Hecht The document provides an overview of integration and acceptance testing, comparing integration tests and acceptance tests. It discusses various testing tools and frameworks for Ruby on Rails including Test::Unit, Webrat, Capybara, Selenium, Cucumber, and FitNesse. It provides information on installing and using these tools for testing end-to-end functionality and interactions across multiple layers.
Behavior Driven Development - TdT@Cluj #15
Behavior Driven Development - TdT@Cluj #15Tabăra de Testare This document discusses Behavior Driven Development (BDD) using the Ruby programming language. It provides an overview of test-driven development (TDD), then defines BDD as building upon TDD by formalizing good TDD habits like working outside-in from business goals. Gherkin is introduced as the language used for writing Cucumber features, using examples to clarify requirements. Cucumber is a tool for running automated acceptance tests written in a BDD style using Gherkin. It also discusses using Capybara to access and interact with web pages in tests.
Tdd
Tddsweekar Attavar K This document discusses test-driven development (TDD) and testing approaches for Ruby on Rails projects. It introduces TDD as writing test code before development code to ensure requirements are met. Common testing frameworks for Rails like RSpec and Cucumber are presented. RSpec is highlighted for its ease of use and features to support TDD. The document also covers concepts like the red-green-refactor TDD cycle and using tools like Factory Girl to generate test data.
Rspec presentation
Rspec presentationMyo T Kyaw This document discusses RSpec, a testing framework for Ruby. It begins by explaining what RSpec is and its Given-When-Then structure. It then provides details on setting up and using RSpec with Ruby, Rails, controllers, models, and features tests using Capybara. Tips are given on FactoryGirl, fixtures, Guard, and configuring .rspec. Matchers, cheatsheets, and resources for learning more are also referenced.
More from Hiroshi SHIBATA (20)
Introduction of Cybersecurity with Ruby at RedDotRubyConf 2024
Introduction of Cybersecurity with Ruby at RedDotRubyConf 2024Hiroshi SHIBATA I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Long journey of Ruby Standard library at RubyKaigi 2024
Long journey of Ruby Standard library at RubyKaigi 2024Hiroshi SHIBATA Ruby has a lot of standard libraries from Ruby 1.8. I promote them democratically with GitHub today via default and bundled gems. So, I'm working to extract them for Ruby 3.4 continuously and future versions. It's long journey for me.
After that, some versions may suddenly happen LoadError at require when running bundle exec or bin/rails, for example matrix or net-smtp. We need to learn what's difference default/bundled gems with standard libraries.
In this presentation, I will introduce what's the difficult to extract bundled gems from default gems and the details of the functionality that Ruby's require and bundle exec with default/bundled gems. You can learn how handle your issue about standard libraries.
Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024Hiroshi SHIBATA I will introduce what's the difficult to extract bundled gems from default gems and the details of the functionality that Ruby's require and bundle exec with default/bundled gems. You can learn how handle your issue about standard libraries.
Deep dive into Ruby's require - RubyConf Taiwan 2023
Deep dive into Ruby's require - RubyConf Taiwan 2023Hiroshi SHIBATA Since Ruby's bundled and default gems change every year with each release, some versions may suddenly happen LoadError at require when running bundle exec or bin/rails, for example matrix or net-smtp.
In this presentation, I will introduce the details of the functionality that extends Ruby's require to provide guidance to users on what they can do to load them. And I will also show how $LOAD_PATH is build behind Ruby and Rails by Bundler.
How resolve Gem dependencies in your code?
How resolve Gem dependencies in your code?Hiroshi SHIBATA This document contains the slides for a presentation on resolving gem dependencies in Ruby code. It discusses RubyGems and Bundler, which are package managers for Ruby that handle dependency resolution. Key terms are defined, like gem, gemspec, Gemfile, and various components involved in dependency resolution like the resolver, resolver engine, and different engines used by RubyGems and Bundler. Performance issues with RubyGems are also addressed, and how Bundler helps address them.
How resolve Gem dependencies in your code?
How resolve Gem dependencies in your code?Hiroshi SHIBATA The document discusses resolving gem dependencies in Ruby code. It begins with an introduction to ANDPAD and then defines key terms related to package managers and gem dependency resolution. It describes the architecture of RubyGems and Bundler and some current issues, such as performance problems and cases where `bundle update` or `gem install` do not work as expected. Deep dives are provided into specific cases to explain underlying causes.
Why ANDPAD commit Ruby and RubyKaigi?
Why ANDPAD commit Ruby and RubyKaigi?Hiroshi SHIBATA https://moneyforward.connpass.com/event/298325/ の発表資料
Dependency Resolution with Standard Libraries
Dependency Resolution with Standard LibrariesHiroshi SHIBATA The document discusses the roadmap for RubyGems and Bundler integration with Ruby 3.0. Key points include:
1) RubyGems 3.1 and Bundler 2.1 were recently released with improvements like lazily loading default gems.
2) Future versions will continue merging the projects, with RubyGems 3.2/Bundler 2.2 integrating into Ruby 2.8.
3) Ruby 3.0 will focus on "gemifying" standard libraries by extracting them to default gems, though some may be excluded.
4) This will require addressing issues around dependency and version resolution for the new default gems.
Roadmap for RubyGems 4 and Bundler 3
Roadmap for RubyGems 4 and Bundler 3Hiroshi SHIBATA The document discusses the roadmap for integrating RubyGems and Bundler, including gemifying standard Ruby libraries for Ruby 3. Key points include:
1) RubyGems and Bundler repositories and teams have been merged into a monorepo to more closely integrate the projects.
2) The roadmap includes releasing RubyGems and Bundler versions simultaneously and potentially bumping to RubyGems 4.0 synchronized with Ruby 3.
3) Standard libraries will be extracted to default gems for Ruby 3, aiming to publish all to default gems except those using internal APIs.
4) Issues around dependency resolution and versioning of default gems need to be addressed in the integration.
Ruby Security the Hard Way
Ruby Security the Hard WayHiroshi SHIBATA 1. The document discusses security topics related to Ruby including defining vulnerabilities, triage policies, and the RubyGems.org workflow.
2. It describes how vulnerabilities are reported and coordinated between developers, and outlines the process of code fixes, releases, and disclosure.
3. Recent attacks on RubyGems.org are reviewed, highlighting account hijacking and typo squatting issues. Solutions discussed include not reusing passwords, using strong unique passwords, and enabling two-factor authentication.
OSS Security the hard way
OSS Security the hard wayHiroshi SHIBATA Hiroshi SHIBATA presented on OSS security at the builderscon 2019 conference. The presentation covered:
1. How Ruby handles releases on a regular schedule and processes for stable and development versions.
2. Policies for triaging vulnerabilities based on impact and developing workflow for coordinated security releases.
3. Recent attacks targeting RubyGems where malicious gems were uploaded by hijacking developer accounts or registering typosquatted gems.
4. Steps users can take to improve security like using strong unique passwords, enabling two-factor authentication, and being wary of code injections in gem installations or native extensions.
The Future of library dependency manageement of Ruby
The Future of library dependency manageement of RubyHiroshi SHIBATA The document discusses the integration of package ecosystems in Ruby. It covers RubyGems and Bundler, which are used to manage library dependencies in Ruby projects. The document outlines challenges with bundler integration and the roadmap for improvements in RubyGems 4.0, Bundler 2.1, and features coming in Ruby 3.0 like pattern matching and gamification of standard libraries.
What's new in RubyGems3
What's new in RubyGems3Hiroshi SHIBATA RubyGems is the package manager for Ruby libraries. Hiroshi Shibata discussed recent changes to RubyGems 3 and 4, as well as integration efforts between RubyGems and Bundler. Key points included making the conservative option default in RubyGems 4, installing gems to the user directory by default, and resolving incompatibilities between dependency resolvers in RubyGems and Bundler. The team is working to merge code bases and integrate command line interfaces.
Gems on Ruby
Gems on RubyHiroshi SHIBATA Hiroshi Shibata gave a presentation on Ruby, RubyGems, and Bundler. He discussed his work on the Ruby core team maintaining Ruby versions like 2.6. He then covered updates to RubyGems including version 3 and the upcoming version 4. Finally, he talked about Bundler 2 and efforts to better integrate RubyGems and Bundler.
RubyGems 3 & 4
RubyGems 3 & 4Hiroshi SHIBATA The document summarizes the key points about RubyGems 3 & 4 from Hiroshi SHIBATA's presentation at RubyKaigi 2018. It discusses RubyGems 2.7, including support for older Ruby versions. It then covers plans for RubyGems 3.0, such as removing deprecated code, and RubyGems 4.0, which may include non-backwards compatible changes.
How to distribute Ruby to the world
How to distribute Ruby to the worldHiroshi SHIBATA The secret of Release story discusses how Ruby is released and distributed to the world. It covers:
1. The Ruby core team which maintains and releases Ruby.
2. The release cycle and process which aims to release every Christmas with preview releases and backporting of fixes.
3. The *.ruby-lang.org domains which are controlled by Matz and host official Ruby resources like documentation, packages, and repositories.
4. Tools for installing Ruby from source like rbenv and ruby-build.
5. Experimental Ruby snap packages which package Ruby as self-contained binaries.
6. Plans to migrate the source code repository from Subversion to Git hosted on git.ruby-lang.org.
Recently uploaded (20)
Supercharge Your AI Development with Local LLMs
Supercharge Your AI Development with Local LLMsFrancesco Corti In today's AI development landscape, developers face significant challenges when building applications that leverage powerful large language models (LLMs) through SaaS platforms like ChatGPT, Gemini, and others. While these services offer impressive capabilities, they come with substantial costs that can quickly escalate especially during the development lifecycle. Additionally, the inherent latency of web-based APIs creates frustrating bottlenecks during the critical testing and iteration phases of development, slowing down innovation and frustrating developers.
This talk will introduce the transformative approach of integrating local LLMs directly into their development environments. By bringing these models closer to where the code lives, developers can dramatically accelerate development lifecycles while maintaining complete control over model selection and configuration. This methodology effectively reduces costs to zero by eliminating dependency on pay-per-use SaaS services, while opening new possibilities for comprehensive integration testing, rapid prototyping, and specialized use cases.
MuleSoft RTF & Flex Gateway on AKS – Setup, Insights & Real-World Tips
MuleSoft RTF & Flex Gateway on AKS – Setup, Insights & Real-World TipsPatryk Bandurski This presentation was delivered during the Warsaw MuleSoft Meetup in April 2025.
Paulina Uhman (PwC Polska) shared her hands-on experience running MuleSoft Runtime Fabric (RTF) and Flex Gateway on Azure Kubernetes Service (AKS).
The deck covers:
What happens after installation (pods, services, and artifacts demystified)
Shared responsibility model: MuleSoft vs Kubernetes
Real-world tips for configuring connectivity
Key Kubernetes commands for troubleshooting
Lessons learned from practical use cases
🎙️ Hosted by: Patryk Bandurski, MuleSoft Ambassador & Meetup Leader
💡 Presented by: Paulina Uhman, Integration Specialist @ PwC Polska
John Carmack’s Notes From His Upper Bound 2025 Talk
John Carmack’s Notes From His Upper Bound 2025 TalkRazin Mustafiz Source: https://docs.google.com/document/d/1-Fqc6R6FdngRlxe9gi49PRvU97R83O7ZTN_KFXo_jf0/
Agentic AI - The New Era of Intelligence
Agentic AI - The New Era of IntelligenceMuzammil Shah This presentation is specifically designed to introduce final-year university students to the foundational principles of Agentic Artificial Intelligence (AI). It aims to provide a clear understanding of how Agentic AI systems function, their key components, and the underlying technologies that empower them. By exploring real-world applications and emerging trends, the session will equip students with essential knowledge to engage with this rapidly evolving area of AI, preparing them for further study or professional work in the field.
European Accessibility Act & Integrated Accessibility Testing
European Accessibility Act & Integrated Accessibility TestingJulia Undeutsch Emma Dawson will guide you through two important topics in this session.
Firstly, she will prepare you for the European Accessibility Act (EAA), which comes into effect on 28 June 2025, and show you how development teams can prepare for it.
In the second part of the webinar, Emma Dawson will explore with you various integrated testing methods and tools that will help you improve accessibility during the development cycle, such as Linters, Storybook, Playwright, just to name a few.
Focus: European Accessibility Act, Integrated Testing tools and methods (e.g. Linters, Storybook, Playwright)
Target audience: Everyone, Developers, Testers
Big Data Analytics Quick Research Guide by Arthur Morgan
Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
The fundamental misunderstanding in Team Topologies
The fundamental misunderstanding in Team TopologiesPatricia Aas In this talk I will break down the argument presented in the book and argue that it is fundamentally ill-conceived, building on weak and erroneous assumptions. And that this leads to a "solution" that is not only flawed, but outright wrong, and might cost your organization vast sums of money for far inferior results.
Cyber security cyber security cyber security cyber security cyber security cy...
Cyber security cyber security cyber security cyber security cyber security cy...pranavbodhak Cyber security
Reducing Bugs With Static Code Analysis php tek 2025
Reducing Bugs With Static Code Analysis php tek 2025Scott Keck-Warren Have you ever deployed code only to have it causes errors and unexpected results? By using static code analysis we can reduce, if not completely remove this risk. In this session, we'll discuss the basics of static code analysis, some free and inexpensive tools we can use, and how we can run the tools successfully.
Splunk Leadership Forum Wien - 20.05.2025
Splunk Leadership Forum Wien - 20.05.2025Splunk Splunk Leadership Forum in Wien vom 20.05.2025
Sprecher: Philipp Putz
AI in Java - MCP in Action, Langchain4J-CDI, SmallRye-LLM, Spring AI
AI in Java - MCP in Action, Langchain4J-CDI, SmallRye-LLM, Spring AIBuhake Sindi This is the presentation I gave with regards to AI in Java, and the work that I have been working on. I've showcased Model Context Protocol (MCP) in Java, creating server-side MCP server in Java. I've also introduced Langchain4J-CDI, previously known as SmallRye-LLM, a CDI managed too to inject AI services in enterprise Java applications. Also, honourable mention: Spring AI.
Multistream in SIP and NoSIP @ OpenSIPS Summit 2025
Multistream in SIP and NoSIP @ OpenSIPS Summit 2025Lorenzo Miniero Slides for my "Multistream support in the Janus SIP and NoSIP plugins" presentation at the OpenSIPS Summit 2025 event.
They describe my efforts refactoring the Janus SIP and NoSIP plugins to allow for the gatewaying of an arbitrary number of audio/video streams per call (thus breaking the current 1-audio/1-video limitation), plus some additional considerations on what this could mean when dealing with application protocols negotiated via SIP as well.
John Carmack’s Slides From His Upper Bound 2025 Talk
John Carmack’s Slides From His Upper Bound 2025 TalkRazin Mustafiz Source: https://docs.google.com/presentation/d/1GmGe9ref1nxEX_ekDuJXhildpWGhLEYBMeXCclVECek/edit?usp=sharing
Offshore IT Support: Balancing In-House and Offshore Help Desk Technicians
Offshore IT Support: Balancing In-House and Offshore Help Desk Techniciansjohn823664 In today's always-on digital environment, businesses must deliver seamless IT support across time zones, devices, and departments. This SlideShare explores how companies can strategically combine in-house expertise with offshore talent to build a high-performing, cost-efficient help desk operation.
From the benefits and challenges of offshore support to practical models for integrating global teams, this presentation offers insights, real-world examples, and key metrics for success. Whether you're scaling a startup or optimizing enterprise support, discover how to balance cost, quality, and responsiveness with a hybrid IT support strategy.
Perfect for IT managers, operations leads, and business owners considering global help desk solutions.
Cognitive Chasms - A Typology of GenAI Failure Failure Modes
Cognitive Chasms - A Typology of GenAI Failure Failure ModesDr. Tathagat Varma My talk on Cognitive Chasms at the brownbag session inside Walmart
Build your own NES Emulator... with Kotlin
Build your own NES Emulator... with KotlinArtur Skowroński For those who have ever wanted to recreate classic games, this presentation covers my five-year journey to build a NES emulator in Kotlin. Starting from scratch in 2020 (you can probably guess why), I’ll share the challenges posed by the architecture of old hardware, performance optimization (surprise, surprise), and the difficulties of emulating sound. I’ll also highlight which Kotlin features shine (and why concurrency isn’t one of them). This high-level overview will walk through each step of the process—from reading ROM formats to where GPT can help, though it won’t write the code for us just yet. We’ll wrap up by launching Mario on the emulator (hopefully without a call from Nintendo).
Master tester AI toolbox - Kari Kakkonen at Testaus ja AI 2025 Professio
Master tester AI toolbox - Kari Kakkonen at Testaus ja AI 2025 ProfessioKari Kakkonen My slides at Professio Testaus ja AI 2025 seminar in Espoo, Finland.
Deck in English, even though I talked in Finnish this time, in addition to chairing the event.
I discuss the different motivations for testing to use AI tools to help in testing, and give several examples in each categories, some open source, some commercial.
Introducing Ensemble Cloudlet vRouter
Introducing Ensemble Cloudlet vRouterAdtran Adtran’s new Ensemble Cloudlet vRouter solution gives service providers a smarter way to replace aging edge routers. With virtual routing, cloud-hosted management and optional design services, the platform makes it easy to deliver high-performance Layer 3 services at lower cost. Discover how this turnkey, subscription-based solution accelerates deployment, supports hosted VNFs and helps boost enterprise ARPU.
What is DePIN? The Hottest Trend in Web3 Right Now!
What is DePIN? The Hottest Trend in Web3 Right Now!cryptouniversityoffi DePIN = Real-World Infra + Blockchain
DePIN stands for Decentralized Physical Infrastructure Networks.
It connects physical devices to Web3 using token incentives.
How Does It Work?
Individuals contribute to infrastructure like:
Wireless networks (e.g., Helium)
Storage (e.g., Filecoin)
Sensors, compute, and energy
They earn tokens for their participation.
MCP Dev Summit - Pragmatic Scaling of Enterprise GenAI with MCP
MCP Dev Summit - Pragmatic Scaling of Enterprise GenAI with MCPSambhav Kothari MCP Dev Summit Talk By Sambhav Kothari - Head of AI Productivity at Bloomberg.
Leave end-to-end testing to Capybara
- 1. Leave end-to- end testing to Capybara SHIBATA Hiroshi Eiwa System Management,Inc.
- 3. SHIBATA Hiroshi a.k.a hsbt [email protected] tDiary commiter
- 5. asakusa.rb
- 19. Capybara
- 21. Capybara
- 25. RSpec runner cucumber runner cucumber DSL(ja) RSpec DSL cucumber DSL capybara
- 26. RSpec Example
- 27. DSL feature ' ' do background do setup_tdiary end scenario ' ' do visit '/' within('title') do page.should have_content(' ') } end within('h1') do page.should have_content(' ') end page.should have_css('a[href="update.rb"]') end end
- 28. Cucumber Example
- 30. Driver
- 32. Driver
- 35. HtmlUnit
- 41. require ‘capybara/dsl’ RSpec.configure do |config| config.include Capybara config.before(:all, :selenium => true) do Capybara.current_driver = :selenium end end
- 44. best mix
- 45. DSL config.before(:all, :selenium => true) do Capybara.current_driver = :selenium end config.after(:all, :selenium => true) do Capybara.use_default_driver end
- 46. DSL feature " ", :selenium => true do let!(:administrator) { User.make! } before do login_as administrator visit new_admin_user_path end scenario " " do ( ) end end
- 47. capybara/rspec
- 48. DSL feature " ", :driver => :akephalos do scenario " " do ( ) end end feature " ", :js => true do scenario " " do ( ) end end => :driver = :selenium
- 49. !!!
- 52. RubyKaigi 2011
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n