Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

The first open-source implementation of the paper that will change automatic test generation is now available! In February, Meta published a paper introducing a tool to automatically increase test coverage, guaranteeing improvements over an existing code base. This is a big deal, but Meta didn't release the code. Fortunately,...

774,460 görüntüleme • 2 yıl önce •via X (Twitter)

10 Yorum

Itamar Friedman profil fotoğrafı
Itamar Friedman2 yıl önce

Hey 👋, one of the Cover-Agent creators here. I've recorded 5 minutes video explaining and reviewing TestGen-LLM and Cover-Agent:

Santiago profil fotoğrafı
Santiago2 yıl önce

Great job and thank you!

Sam Francisco profil fotoğrafı
Sam Francisco2 yıl önce

It's 630 why are you giving me more work already Santiago I haven't even had my coffee yet

Santiago profil fotoğrafı
Santiago2 yıl önce

lol

Alex Dillon | Quality Advocate profil fotoğrafı
Alex Dillon | Quality Advocate2 yıl önce

As someone very much involved in testing, this is quite interesting to me. I want to look more into it and explore the quality of the tests. Though, I’m a bit skeptical that this will be replacing someone having to write these tests, the hope is that it at least provides a good starting point for someone.

Graham Cox (@grahamcox82.bsky.social) profil fotoğrafı
Graham Cox (@grahamcox82.bsky.social)2 yıl önce

I'm curious - how does the tool know what the correct behaviour is? Or does it assume that the current implementation is already correct? (Which, to be fair, is how things like Jest snapshots work anyway)

Shikhar Srivastava profil fotoğrafı
Shikhar Srivastava2 yıl önce

As someone who doesn’t like TDD..

Pradeep Gowda profil fotoğrafı
Pradeep Gowda2 yıl önce

@ponnappa fyi

Markus Odenthal profil fotoğrafı
Markus Odenthal2 yıl önce

This can be especially helpful for ML projects. I usually write tests when I bring my product to production, not when starting the project. So this would be a huge time-saver, thanks for sharing.

SwissTechMind profil fotoğrafı
SwissTechMind2 yıl önce

So, if I understand correctly, the primary purpose of these tests is to safeguard against unintentional changes, right?

Benzer Videolar

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Tibor Blaho

136,026 görüntüleme • 1 yıl önce

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

38,880 görüntüleme • 23 gün önce