bitly

🗜 A Ruby wrapper for the bit.ly API

Runs with mockssource: GitHubhomepageRubyMITcommit 3fb9585c2558

Ruby, MIT licensed. The project labels itself: api client, api wrapper, bitly, bitly api, bitly v4, shorten urls and url shortener.

bitly runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The bitly gem installs and builds on a portable Ruby 3.2.3, its 162-example RSpec suite passes with 0 failures, and shorten/expand/user/error paths were exercised end-to-end against a schema-correct local mock API.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.25 (measured)
recorded runs
1
last tested
stars
448
forks
135
open issues
2
watchers
10
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing bitly, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • No Ruby interpreter in container12 minutes
  • OAuth access_token under WebMock: faraday-net_http 3.5.0 incompatible with webmock 3.7.6 (wrong number of arguments (given 2, expected 1))4 minutes
  • Native extensions failed: mkmf can't find ruby.h (no ruby-dev headers)3 minutes
  • psych.so missing libyaml-0.so.2 / readline.so missing libncurses.so.63 minutes
Install time
25 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
bundle exec rspec -> 162 examples, 0 failures; ruby -Ilib /tmp/verify_mock.rb -> SHORTEN link=https://bit.ly/mock123 long_url=https://example.com/shorten-me; EXPAND long_url=https://example.com/expanded; USER login=mockuser; VERIFY_OK
Model tokens used
976,167
Exact commit tested
3fb9585c2558
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- The container had no Ruby, and system package installs are impossible without root (`apt-get inst…
- Ran `bundle install` — first failure was missing Ruby dev headers (`mkmf.rb can't find header fil…
- Ran the test suite: `bundle exec rspec` → `162 examples, 0 failures` (also via `bundle exec rake …
- Stand up a schema-correct mock Bitly v4 API (WEBrick) on `127.0.0.1:8899` (shorten/expand/user) p…
- One note: the repo's OAuth `access_token` path uses the oauth2 gem with a hardcoded `https://api-…
- Left the repo untouched (`git status` clean).
**Result**
- install_succeeded: true
- launch_succeeded: true
- test_depth: tier2_mock
- verified_how: `bundle exec rspec` → `162 examples, 0 failures`; and a Ruby script hitting the moc…
- final_state: The bitly gem builds and installs on a portable Ruby 3.2.3, its full 162-example RSp…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 25 minutes to install, slower than the median of the 39 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 40 api-client projects Argusic has installed and timed, bitly was the 37th fastest to reach a running state, and 25 of 40 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.25

Topics (from GitHub)

api-clientapi-wrapperbitlybitly-apibitly-v4shorten-urlsurl-shortener

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/bitly.svg)](https://argusic.com/subject/bitly)

Questions

Does bitly run?
bitly runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test bitly?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3fb9585c2558. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test bitly?
The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does bitly take to install?
25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does bitly need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing bitly?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does bitly compare with the alternatives?
Of the 40 api-client projects Argusic has installed and timed, bitly was the 37th fastest to reach a running state, and 25 of 40 reached one at all.
Where is the evidence for bitly?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion