factory_bot
AutoFixture
factory_bot | AutoFixture | |
---|---|---|
30 | 11 | |
7,875 | 3,226 | |
0.1% | 0.7% | |
7.8 | 4.6 | |
5 days ago | 20 days ago | |
Ruby | C# | |
MIT License | MIT License |
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.
factory_bot
-
Show HN: Factory-JS – TypeScript dummy object generator for testing
I made Factory-js inspired by factory-bot (https://github.com/thoughtbot/factory_bot), supports Prisma and Drizzle ORM and more. TypeScript is now widely used in both backend and frontend, but there is no de facto standard factory library. I'm developing a web application using Prisma, trpc, and nextjs, but I was struggling with how to write more beautiful and readable back-end tests. That's why I made factory-js.
-
Metaprogramming in Ruby: Advanced Level
factory_bot: A fixtures replacement
-
Seeding the DB: Best approach?
Not sure if you want the execution speed to be faster, or the development speed. If it's development, you can use FactoryBot in a script to generate data easily once you have your factories set up.
-
How could I prevent resetting the database during the test?
For instance, thoughtbot/factory_bot.
-
You can’t bribe, threaten, or feed people to get them back in the office
> if you're a bunch of tool makers and you all know your audience of tool users then there's no benefit at all to have someone offended by the word "tool" in your workforce.
It kinda reminds me of the factorygirl -> factorybot [0] story. It was a cute enough name for a technical tool that plays nice among bros, and down the line you end up renaming your package and deal with the drama.
On brand image, I get your point. I think the corporations doing it best tend to juggle with multiple brands and segment their market accordingly. Then yes, an homogeneous, single focus brand will be more valuable, as it also help to push people outside of the target to your other brands.
[0] https://github.com/thoughtbot/factory_bot/wiki
-
rspec testing on Windows.
Not sure I follow why this question is related to an OS like Windows, but when it comes to RSpec testing with different users, I would use Factory Bot and define a User Factory and add Traits such as Admin & Non Admin and use them in specs with their pre-defined attributes to what they can access based on your User Model and call them within the specs.
-
How to optimize factory creation.
The factory-bot gem is used in almost in all of our spec files and it make our set up much more easier than when we use fixtures. Here is the tradeoff, the easier the gem is to use, the more likely you’ll end up with some pain to control its usage. And when the times come to tackle slow tests, the best bet you can take is to start digging into you factories because it’s likely they are the primary reason why your test suite is slowing down
-
Efate Test Generator Series: Extending the library
Efate is actually the second test fixture library I've written and there were several lessons I learned after using the first iteration for several years myself. The first version was influenced a great deal by factor_girl (called factory_bot now), with a heavy dependency on strings to define and create the fixtures. It also wasn't very modular. You couldn't just import a specific fixture, you had to bring in the whole library. And it wasn't very extensible, if you needed to define custom behavior for how a field should be created, it wasn't very pretty.
-
Get help from thoughtbot for free (mentoring / office hours)
I work at thoughtbot, you might know us for our open source work like administrate, factory_bot or shoulda-matchers.
-
Gnarly Learnings From June 2022
As we continue to level-up our skillsets as developers in Rails, the utility of POROs (Plain Old Ruby Objects) becomes more apparent and appealing. Sometimes, the business object(s) you create do not require persistent storage to a database and are, therefore, outside of the scope of an ORM (Object Relational Mapper) like ActiveRecord. But how do we maintain simplicity in our test suite and continue to leverage helpful testing libraries like FactoryBot without one? This instructional article explores how to implement factories for POROs including common pitfalls, building nested resources, and factory linting.
AutoFixture
-
API: Go, .NET, Rust
Yes, it does feel like some of the "standard stuff" in other more nuanced languages are missing (especially miss AutoFixture ngl). Some of those are a conscious decison by the golang team for example.
-
Integration Testing Postgres Store
Our first test is very easy, I like to name my tests as MethodName_GivenCondition_ShouldExpectedResult to follow the pattern, I have added GetById_GivenRecordDoesNotExist_ShouldReturnNull and I am going to leavarage excellent AutoFixture to get a new Guid as parameter. For this test we don't need arrange part, we would skip to the act and then assert. For Assertion I am going to use FluentAssertions. For this test we need to assert the returned result is null.
-
Setting up a simple testing project with C#
The next test to talk about, is that if this was a bank, we would have multiple customers, who can hold multiple accounts that we need to calculate the interest for. You could manually construct these objects if you want, but I'm going to use a package called AutoFixture to make life easier.
-
AutoFixture Tips and Tricks
AutoFixture is an amazing library that simplifies the process of creating test data in .NET. If for some reason you don't use this fantastic tool, it's time to consider it. Today, I'm going to share some tips for using AutoFixture that will be beneficial for developers of all skill levels. Let's get started!
- Integration tests without API dependencies with ASP.NET Core and WireMock.Net
-
I need a C# crash course for experienced developers
AutoFixture
-
Reduce your tests cognitive complexity with AutoFixture
Ensuring that your test is still readable and not bloated by the setup of those variables may be quite a challenge but hopefully no more with AutoFixture, let's see how!
-
Practical complex data for unit testing
One neat library for creating and generating test data is AutoFixture. The creators describe it as follows:
-
14 .NET packages I always recommend
First time I heard of Bogus, looks interesting, been using AutoFixture for those will definitely take a look at it.
- LPT: There is a library called Bogus, you should know it exists much earlier than I did in my career.
What are some alternatives?
Fabrication - This project has moved to GitLab! Please check there for the latest updates.
Bogus - :card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js.
faker - A library for generating fake data such as names, addresses, and phone numbers.
NSubstitute - A friendly substitute for .NET mocking libraries.
ffaker - Faker refactored.
FakeItEasy - The easy mocking library for .NET
Machinist - Fixtures aren't fun. Machinist is.
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
Forgery - Easy and customizable generation of forged data.
NBuilder - Rapid generation of test objects in .NET
Fake Person - Create some fake personalities
FsCheck - Random Testing for .NET