DOOM-3-BFG
minitest
DOOM-3-BFG | minitest | |
---|---|---|
18 | 10 | |
4,739 | 3,243 | |
0.9% | 0.2% | |
0.0 | 8.0 | |
3 days ago | 21 days ago | |
C++ | Ruby | |
GNU General Public License v3.0 only | 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.
DOOM-3-BFG
-
How to comply with OSS licenses without declaring which libraries you used?
The Bethesda representative said that they do not publish which OSS libraries they use but that they comply with any notice requirements. I admit, the claim on my side is somewhat thin, but there is one third party library (Base64.cpp) in DOOM 3 BFG that requires notice and states:
-
Where is Bethesda hiding their third party notices?
Even idTech 3 used third party components as listed in the description here: https://github.com/id-Software/DOOM-3-BFG. Newer versions of idTech use Vulkan for rendering. For that, they are basically forced to included the header files of Vulkan which are licensed under Apache 2. So it has to be mentioned somewhere.
-
Initialization in Modern C++ (295 pages)
I guess you can still write valuable software, even more complex than most people can write, with simple (03) C++. Like Doom 3: https://github.com/id-Software/DOOM-3-BFG
> What you are describing
On the other hand, I believe what you are describing is the exact meaning of FUD. In that precise order: "in C++ they have serious consequences" is fear, "There are bugs in the code--probably in your code--right now" is uncertainty, and "Some might be CVEs" is doubt.
-
You can play Doom 3 in a web browser
According to https://github.com/id-Software/DOOM-3-BFG
-
Question about certain games
Doom 3 was released in 2004. The engine has come to be known as "Id Tech 4", and it's open source. Written mostly in C++, looks like.
- How advance is the code in the average game?
-
Which piece of software you wish it was open source?
Id Tech 4 is currently Open Source (GPL licensed)
- Need help finding resources for id Tech 4(Doom 3 engine)
-
Greatest programs
I believe doom 3 source is published on github so people can have a look for themselves if they want.
-
Ask HN: Codebases with great, easy to read code?
Doom 3 is a perennial favorite for "most beautiful C++ codebase" lists [0]
[0] https://github.com/id-Software/DOOM-3-BFG
minitest
-
Test Driving a Rails API - Part Two
In this part, we’ll set up our testing environment so that we can test our Rails API using minitest with minitest/spec. We’ll look at the differences between traditional style unit tests and spec-style tests, or specs. I’ll demonstrate why you should use minitest-rails. We’ll look at using rack-test for testing our API. We’ll even create our own generator to generate API specs.
-
Where can I learn to deliver a proper solution?
I forgot to mention that reading code is also a good way to learn how to write code, it's like inspiration. Check repos of some gems you like. For example sidekiq https://github.com/sidekiq/sidekiq/tree/main/lib/sidekiq Or minitest https://github.com/minitest/minitest/tree/master/lib/minitest
-
I_suck_and_my_tests_are_order_dependent
All through GitHub.
1. From https://github.com/rails/rails/blob/6ffb29d24e05abbd9ffe3ea9..., click "Blame" on the header bar over the file contents.
2. Scroll down to the line and click on the commit in the left column.
3. Scroll down to the file that removed the line from its previous file, activesupport/lib/active_support/test_case.rb.
4. Click the three-dots menu in that file's header bar and select "View file".
5. Click "History" in the header bar of the contributors, above the file contents.
6. I guessed here at commit 281f488 on its message: "Use the method provided by minitest to make tests order dependent". There's a comment here that identified the problem which led to, and provided context for, the change in 6ffb29d.
The OP is from minitest's documentation, so to find the introduction in minitest, it's basically the same process.
1. Go to https://github.com/minitest/minitest.
2. Search the repo for the method name. Even just "i_suck" will match the commit.
3. Select the oldest commit in the results. That's a4553e2.
-
Minitest, we've been doing it wrong?
The new test convention is now "test/**/test_*.rb" instead of "test/**/*_test.rb". For example, Puma and Minitest are popular repositories using this naming pattern.
-
Ask HN: Codebases with great, easy to read code?
https://github.com/seattlerb/minitest really removed the FUD for me when i started learning Ruby and Rails. Its full of metaprogramming and fancy tricks but is also quite small, practical and informal in its style.
e.g. "assert_equal" is really just "expected == actual" at it's core but it uses both both a block param (a kind of closure) for composing a default message and calls "diff" which is a dumb wrapper around the system "diff" utility (horrors!). There is even some evolved nastiness in there for an API change that uses the existing assert/refute logic to raise an informative message. this is handled with a simple if and not some sort of complex hard-to-follow factory pattern or dependency injection misuse.
https://github.com/seattlerb/minitest/blob/master/lib/minite...
-
49 Days of Ruby: Day 46 -- Testing Frameworks: Minitest
Those are just a few examples of what you can do with Minitest! Check out their README on GitHub and keep on exploring.
-
Ruby through the lens of Go
One of the things I love the most about Ruby is that it tends to coalesce around one or two really popular libraries. Rails is the big one obviously, but over time you see libraries designed for a particular purpose "winning" over other things. This includes things like linting/code analysis (Rubocop), authentication (Devise), testing (RSpec and Minitest) and more. The emphasis is on making something good great rather than making a lot of different good things.
-
Best way to learn testing in RSpec?
Then try minitest (unit and spec verisons) https://github.com/seattlerb/minitest
What are some alternatives?
RBDOOM-3-BFG - Doom 3 BFG Edition source port with updated DX12 / Vulkan renderer and modern game engine features
Test::Unit - test-unit
Quake-2 - Quake 2 GPL Source Release
RSpec - RSpec meta-gem that depends on the other components
Quake-III-Arena - Quake III Arena GPL Source Release
Cucumber - A home for issues that are common to multiple cucumber repositories
awesome-dotnet - A collection of awesome .NET libraries, tools, frameworks and software
Pundit Matchers - A set of RSpec matchers for testing Pundit authorisation policies.
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
shoulda-matchers - Simple one-liner tests for common Rails functionality
AspNetCore.BookStore - ASP.NET Core application using Command Pattern and Repository Pattern
Aruba - Test command-line applications with Cucumber-Ruby, RSpec or Minitest.