selenium.cr
Selenium library for Crystal (by crystal-loot)
spectator
Feature-rich testing framework for Crystal inspired by RSpec. (by icy-arctic-fox)
| selenium.cr | spectator | |
|---|---|---|
| - | 1 | |
| 23 | 95 | |
| - | - | |
| 4.1 | 6.7 | |
| 23 days ago | 3 months ago | |
| Crystal | Crystal | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
selenium.cr
Posts with mentions or reviews of selenium.cr.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning selenium.cr yet.
Tracking mentions began in Dec 2020.
spectator
Posts with mentions or reviews of spectator.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-01.
-
What are the downsides of Ruby ?
In that situation, if there was a performance critical component we wanted to optimize by rewriting in Crystal, we would first extract it into its own app or worker (aka breakup the monolith, aka micro-services). Additional apps could have requests routed to them via a reverse proxy or they could be internal HTTP-endpoints. Then we would port that code to Crystal, replacing gem dependencies with Crystal shards equivalents (which there are many, and more are being added everyday), and then running the Ruby code through rubycodemod_crystal which changes minor things (ex: include? -> includes? or require 'foo' -> require "foo"). Assuming this component has RSpec tests, I would convert them to Spectator which is a Crystal clone of RSpec. Then I would tighten up the Crystal code by adding explicit Types to all instance variables and method signatures, so the compiler doesn't have to infer the types. This is basically the same process I have done when porting some of my own Ruby libraries to Crystal.
What are some alternatives?
When comparing selenium.cr and spectator you can also consider the following projects:
mocks.cr - General purpose mocking library for Crystal.
spec - Common/helpful Spec compliant testing utilities
minitest.cr - Test Unit for the Crystal programming language
spec-kemal - Easy testing for Kemal
microtest - Small test framework, because it has power asserts as the only assertion.
crytic - Mutation testing for crystal.
crystal - The Crystal Programming Language
coverage - Coverage tool for Crystal lang
ruby_crystal_codemod - A codemod / transpiler that can help you convert Ruby into Crystal
scar - A game engine written in Crystal using crsfml