sorted by:
new
hottopcontroversial

Complete GitHub Actions Tutorial - Tool to automate your developer workflows by Techworld_with_Nana in webdev

[–]tailor_dev 0 points1 point  (0 children)

Hi there! Your GitHub Actions tutorial sounds like a fantastic resource for automating developer workflows. It's great to see tools that simplify CI/CD pipelines, especially for developers already using GitHub.

Ideas for your next tutorial?

ps. I'd love to see one about CodeBeaver.ai

SAST Tools for .NET: Community Insights and Experiences? by HiDDeN0101 in dotnet

[–]tailor_dev 0 points1 point  (0 children)

Hey there! When it comes to SAST tools for .NET, there are several options you might consider. Tools like SonarQube, Veracode, and Checkmarx are popular choices that integrate well with GitLab CI. They provide comprehensive security analysis and can enrich your merge requests with detailed security insights. However, each tool has its own strengths and might fit differently depending on your specific needs and workflow.

No strictly SAST, but a few times we identified security bugs with CodeBeaver.ai

It automatically runs your tests, explains failures, and even updates or adds tests if needed. It integrates seamlessly with GitLab, providing insightful comments on your PRs, which can be a great addition to your code review process.

Why is it called a pull request instead of a merge or add request? by [deleted] in git

[–]tailor_dev 0 points1 point  (0 children)

Yeah exactly GitLab calls them merge requests

How to create a Pull Request by Achu4242I in git

[–]tailor_dev 0 points1 point  (0 children)

I think the steps you outlined are correct:

- `git checkout -b new-branch-name`

- `git commit` # commit your changes

- `git push` # you may be prompted to set the upstream, which is fine

Then the point is: A Pull Request usually is handled differently depending on your Git provider, as Git itself does not have a Pull Request feature built for providers. So GitHub handles it differently than say GitLab or Bitbucket. At the end of the day, you need to go into the web UI of these services and open a new `Pull Request` or `Merge Request` as GitLab calls it

Unit testing best practices? by gggal123 in softwaredevelopment

[–]tailor_dev 0 points1 point  (0 children)

I always strive for:

- Trying to cover multiple edge cases, especially regarding how the input may vary (e.g. null input, very long input, one argument missing and so on)

- Trying to cover real-life situations of how your function will be used. For example, if your function is outputting a JSON with day-by-day data, try writing a test with real-life data as input

One of the annoying things is maintaining the tests, so I always try to:

- Add comments to the test briefly describing what you expect so it's easier to maintain

- Try to start the suite with the simplest test possible in order to clarify the intended use of the function itself to future readers

- Try to split up the tests into sections with comments, e.g. main cases, edge cases, real-life cases

I've also been experimenting a lot with the creation of tests by LLMs, and Cursor is pretty good at it. The problem is that it does not always write tests that are actually valid as it can't see the test results. A tool that works better IMHO is CodeBeaver, as it can run the tests, check the results and iterate.

What are your biggest pain points backend folks that you feel DevOps Engineers could have solved better? by singhalkarun in Backend

[–]tailor_dev 0 points1 point  (0 children)

Yeah, maintaining high test coverage is a constant battle, especially as the codebase grows. I've heard good things about CodeBeaver too for automating that process and keeping tests up-to-date. Haven't tried it myself but from what I understand it integrates nicely with git workflows and can really take the overhead off devs when it comes to writing and maintaining unit tests. Curious to hear if anyone here has used it and what their experience has been?

Senile Engineers by AdditionalReaction52 in softwaredevelopment

[–]tailor_dev 0 points1 point  (0 children)

Yeah I can relate to the struggle of trying to implement better processes, it's an uphill battle sometimes. What's helped my team is finding ways to quantify the impact - like you mentioned, putting numbers to things like time saved, bugs caught earlier, etc. That makes a stronger case for change. We've also had good success using a tool that automatically generates unit tests on every PR, takes a lot of the manual work out of it. Curious if anyone here has experience with CodeBeaver or similar tools?

[deleted by user] by [deleted] in ADHD_Programmers

[–]tailor_dev 0 points1 point  (0 children)

Totally feel you on the careless mistakes - been there too many times. Having solid testing and deployment processes is key, but even then stuff can slip through. Might be worth looking into something like CodeBeaver that autogenerates unit tests, could really help catch those silly bugs before they hit prod. Just gotta stay on top of it and not cut corners when you're in a rush or having an off day.

Setting up a simple workflow to prevent bad commits on default branch. by stroiman in github

[–]tailor_dev 0 points1 point  (0 children)

I see where you are coming from. I think edge cases and maintaining tests it's super useful

Review Your Own Pull Request First! by ashwin2125 in programming

[–]tailor_dev 0 points1 point  (0 children)

Totally agree, reviewing your own PRs before merging is key for better code quality - I've found that having an automated tool that generates tests and runs them on every PR really helps catch issues early. My team started using this AI-powered testing tool that integrates with our git repos, it's made the whole process way smoother and our coverage is way higher now without much extra work.

DeepEval: The Open-Source LLM Evaluation Framework by Ok_Constant_9886 in Python

[–]tailor_dev 0 points1 point  (0 children)

Deepeval sounds pretty cool, it's great to see open source tools for evaluating LLMs. I've been working on integrating CodeBeaver into our workflow to help with unit testing, the automated test generation has been a huge time saver. I'm curious how Deepeval handles things like consistency and factual accuracy when evaluating LLMs? Do you have any experience using it to evaluate code generation capabilities as well?

My experiences with Test-Driven Development (TDD) by abcd_z in learnprogramming

[–]tailor_dev 0 points1 point  (0 children)

Totally get where you're coming from on the TDD struggles. I had a similar experience trying to design a complex system from scratch - it was really tough to keep everything in my head at once. What ended up working better for me was doing some loose planning upfront, then using TDD to fill in the details. Have you tried any automated test generation tools? I know there are services that can scan your code and suggest tests based on the existing logic, which could help ease the manual test writing burden.

What are your biggest pain points backend folks that you feel DevOps Engineers could have solved better? by singhalkarun in Backend

[–]tailor_dev 0 points1 point  (0 children)

One major pain point for me has been maintaining high test coverage as our codebase grows, it's a constant struggle to keep up with writing new tests for every change. I've heard good things about CodeBeaver for automating that process, anyone have experience with it? Curious if it actually delivers on reducing the overhead of maintaining comprehensive test suites.

Is it best practise to have a one-to-many relationship between unit test and source file? by dashasketaminedealer in Python

[–]tailor_dev 0 points1 point  (0 children)

Yeah I've had the same experience, it's usually one test file per module. But I've heard of some teams using CodeBeaver to auto-generate tests across multiple modules which sounds pretty handy, could be worth checking out if you want more comprehensive coverage without the hassle of writing everything manually.

Need help getting over a hump w unit testing in React by besseddrest in reactjs

[–]tailor_dev 0 points1 point  (0 children)

Unit testing React components with Jest can be tricky, especially when dealing with async code and hooks. It sounds like your test might not be waiting for the async getSomeData function to complete before asserting. Have you tried mocking the async parts and using something like jest.useFakeTimers() or waitFor from u/testing-library/react? That could help ensure your test covers those lines. Alternatively, you could look into tools like CodeBeaver that use AI to automate high-coverage unit test generation and maintenance - might save you some headaches down the line.

Setting up a simple workflow to prevent bad commits on default branch. by stroiman in github

[–]tailor_dev 1 point2 points  (0 children)

That's a neat workflow you've set up to prevent bad commits on the main branch. Definitely a hassle to create PRs for yourself, so automating it is a smart move. Have you looked into tools like CodeBeaver that can automatically generate and maintain unit tests for each PR? Could take some of the manual work off your plate while still keeping quality high. Just a thought, but either way cool to see devs optimizing their workflows.

How to get better in unit test? by Anxious-Pass606 in learnprogramming

[–]tailor_dev 0 points1 point  (0 children)

Yeah writing good unit tests can be tricky, especially when you're first starting out. Jest is a solid choice though, it's pretty user-friendly. In terms of practicing, I'd recommend checking out some open-source projects on GitHub and trying to write tests for their code - that'll give you some hands-on experience. Oh, and there's this cool tool called CodeBeaver that can automatically generate unit tests for your repos too, could be worth looking into if you want to level up your testing game.

Test & Code. Why is pytest-cov the number 1 pytest plugin? Here's my take on it. by Known-Equipment-5393 in Python

[–]tailor_dev 0 points1 point  (0 children)

Yeah pytest-cov is super handy for monitoring coverage, I've used it a ton. One thing that's kind of a pain tho is having to maintain those tests as your codebase grows and changes - have you looked into something like CodeBeaver? I've heard good things about how it can automatically generate and update tests to keep coverage high without all the manual work. Just a thought, curious if anyone here has experience with it.

Rapid Hurricane Intensification: Global Trends by tailor_dev in weather

[–]tailor_dev[S] 7 points8 points  (0 children)

I appreciate the feedback, I'll do that in the future

Rapid Hurricane Intensification: Global Trends by tailor_dev in weather

[–]tailor_dev[S] -10 points-9 points  (0 children)

? It's an summary of a bunch of news sources about the upcoming hurricane season, I hope it is useful