Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Tags: Mocking

1.google / googletest

GoogleTest - Google Testing and Mocking Framework

C++BSD-3-CLAUSE40K total11K forks

+1,384 stars

from 38,322 · score 7.23

2.vektra / mockery

A mock code autogenerator for Go

go
mock
mocking
golang
testing
generator
+5 more

Go BSD-3-CLAUSE7.2K total468 forks

+114 stars

from 7,062 · score 4.74

3.lundberg / respx

Mock HTTPX with awesome request patterns and response side effects 🦋

httpx
testing
pytest
mock

Python BSD-3-CLAUSE844 total69 forks

+55 stars

from 789 · score 4.03

4.harrison314 / BouncyHsm

Bouncy Hsm is a software simulator of HSM and smartcard simulator with HTML UI, REST API and PKCS#11 interface.

blazor
blazor-webassembly
bouncycastle
cryptography
csharp
hsm
+2 more

C#BSD-3-CLAUSE205 total29 forks

+29 stars

from 176 · score 3.40

Mockery is a simple yet flexible PHP mock object framework for use in unit testing with PHPUnit, PHPSpec or any other testing framework. Its core goal is to offer a test double framework with a succinct API capable of clearly defining all possible object operations and interactions using a human readable Domain Specific Language (DSL).

mockery
phpunit
php
stub
mock
mocking
+1 more

PHP BSD-3-CLAUSE11K total470 forks

+26 stars

from 10,698 · score 3.30

6.cpputest / cpputest

CppUTest unit testing and mocking framework for C/C++

cpputest
unit-testing
test-driven-development
c-plus-plus
very-kewl
memory-leak
+1 more

C++BSD-3-CLAUSE1.5K total532 forks

+19 stars

from 1,464 · score 3.00

7.apex-enterprise-patterns / fflib-apex-mocks

An Apex mocking framework for true unit testing in Salesforce, with Stub API support

apex
mock
stub-api
unit-test

Apex BSD-3-CLAUSE462 total231 forks

+4 stars

from 458 · score 1.61

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

A new repository enters the index when it gains stars faster than the published admission threshold, whatever its size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index