Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
-
@Grumm To be entirely honest, a big part of what breaks the tie for me when talking about choosing software are small stuff, such as UI, how some minor feature are designed and such
You can make and break a market by only tweaking with minor changes to an already successful formula! -
@NeatNerdPrime seems too complicated for my needs, but thanks.
@fraktalisman mostly automation. I want to set some rules and have it auto budgeted and categorized. I'm sure someone can do it, but I really hate spreadsheets.
@cho-uc no luck as of yet but I'll post back here when I get the time after work.
From what I found it looks like a mix between a dirty testbed and validations.
What's weird is that I get failures when I run tests the first time, but not again. These are the same failures I get when I introduce any new tests.
@Grumm maybe I used the wrong term. I really want budgeting software.
I plan on having it show when bills are expected due, what ones have been paid, how far into budgets I am, etc.
At this moment it's currency agnostic, built that way so I can track my crypto accounts too, however once I start working on the UI I'll need to have some currency configured for each account. -
I think it's a valiant effort and a good reason to do this. Especially if you write tests to verify all is in order.
Sounds like something is messing with the entire test setup.
Did you try duplicating the existing assertions? If it still craps out it's likely a time related thing. Taking too long to initialise and something times out that sort of thing. The other option is different behaviour after a magic number like 64.
Don't have any experience in ruby or minitest. Do know Perl assertions are quirky, could be you run into some nasty quirk. Hope you figure it out soon so you can get cracking again!
The more you look, the worse it gets
Rails is a shady framework
Building my own accounting software because everything else is overly complicated and is trying to compete with enterprise accounting tools. All I want is some budgeting, some bill tracking, and categorization.
Writing in Ruby because I'm a masochist. Using built-in minitest because again 😈.
I have currently around 62 assertions. As soon as I add ANY new test that's literally asserting true, everything comes unglued and 20+ failures pop up. Take it out, 62 passes.
I feel like I'm going crazy at this point. The errors also don't make ANY sense. Shit like, "that record doesn't exist" when it's clearly a part of fixtures and is only used in ONE test(the one that's breaking).
Installed minitest bisect, and it's like 🤷♀️"lol get fucked bro!"
So I came here to rant about this before my battery dies and I go drink myself to sleep.
Thank you for coming to my dev-talk.
rant
masochist
ruby
wtaf
minitest