130
Rivian blames “fat finger” for infotainment-bricking software update
(arstechnica.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Nov 2023
130 points (97.1% liked)
Technology
59483 readers
1737 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Integration tests don't really help if you just push the wring build to production.
Although the pipeline should probably not accept builds that haven't passed all tests.
This is like designing a deadbolt that tells you that the key doesn't work, but it allows you to open the door anyway. Why would anyone have a process in place where you can push to production with failing integration tests?
I actually work in automotive testing, and the honest truth is that there likely is no real automated pipeline.
Automotive software testing is much more complex than simple software unit or integration tests. You need to run on actual hardware, accompanied by all the other ECUs you are interfacing with. And the tools that slow you to do so are specialized tools, which often are not yet integrated into CI/CD processes (they're pretty much all working on it though). I.e. getting test results for a build involves manual labor, which makes it prone to errors.
You don't think this is a smell? Surely your company can improve on this.
I do, and we are actively working on it.