POPULARITY
Ecco un argomento molto discusso, molti li conoscono ma pochi li usano. Con la puntata di oggi voglio dare il via ad un percorso alla scoperta del mondo dei Test, iniziando oggi con un'introduzione agli Unit Test.https://amzn.to/3TdJFJIhttps://learn.microsoft.com/en-us/visualstudio/test/unit-test-basics?view=vs-2022https://learn.microsoft.com/en-us/visualstudio/test/create-unit-tests-menu?view=vs-2022#visualstudio #unittest #dotnetinpillole #podcast #xunit #nunit #mstest
Nella pillola di oggi vi parlo di Playwright, una libreria per test e2e che ho scoperto da pochissimo. Una libreria davvero utile e completa per testare le nostre applicazioni web, comprese quelle Blazor.https://playwright.dev/https://playwright.dev/dotnet/docs/introhttps://github.com/microsoft/playwright-dotnethttps://www.youtube.com/channel/UC46Zj8pDH5tDosqm1gd7WTghttps://dev.to/puppo/series/20832https://medium.com/younited-tech-blog/end-to-end-test-a-blazor-app-with-playwright-part-1-224e8894c0f3
Servono davvero i test? Perchè li dovremmo scrivere? Vediamo di parlare un pò di questo argomento così sconosciuto, ma di assoluta importanza, specialmente per chi vuole realizzare software che duri nel tempo.https://it.wikipedia.org/wiki/Unit_testinghttps://docs.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-dotnet-test?WT.mc_id=DT-MVP-4021952https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps?WT.mc_id=DT-MVP-4021952https://amerlin.keantex.com/unit-test-in-asp-core-parte-1/
Si sente poco parlare di Unit Test e oggi vi voglio far conoscere un package nuget che può aiutarvi sia nella scrittura, ma anche nel capire il perchè i test falliscono.https://fluentassertions.com/https://github.com/fluentassertions/fluentassertionshttps://github.com/adrianiftode/FluentAssertions.Webhttps://www.ezzylearning.net/tutorial/asp-net-core-unit-testing-with-fluent-assertionshttps://makolyte.com/csharp-use-fluentassertions-to-improve-unit-tests/
Esitono casi in sia difficile testare che modelli complessi o documenti non cambino nel tempo, ed è qui che entra in gioco Verify, una libreria che utilizza degli snapshot per poter testare questi casi.
With part 2 of my open box of NUNIT's homemade cosmetics, I get into a little of the details of using the product, the opinion of its potential and my personal opinion of the product. turns out that its a more than meets the eye. Nunit’s homemade cosmetics offers a variety of hydrating, natural, and exfoliating products for body and lip care. We believe in natural sweetness that hydrates and nourishes , not only the skin but your energy field you emit to everyone.
In this episode of Adventures in .NET the panel shares some of the things they have been doing in their work. Caleb Wells starts by talking about unit testing. His team at work started implementing unit testing he got to do a lot of research for their project. He shares some of the unit testing frameworks he looked at and explains why he chose XUnit. Other tools he is using include MOQ, Bogus and Fluent Assertions. They discuss what these do and how they make unit testing easier. Wai Liu tells Caleb all about GraphQL and why it is better than using a rest API. It is more efficient and cleaner. It is also easy to incorporate into an existing application. Wai also wants to discuss authentication. He explains that there is no need to create custom authentication solutions when there are so many great authentication tools built by people smarter than you. He recommends Firebase Auth by Google. The panel explains the difference between authentication and authorization. Panelists Wai Liu Caleb Wells Sponsors CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links GraphQL-dotnet NET Core 2: Why xUnit and not NUnit or MSTest https://xunit.net/ Quickstart Bogus Firebase Auth https://github.com/graphql-do tnet/graphql-dotnet https://fluentassertions.com/ https://www.ncrunch.net/ www.linkedin.com/in/wai-liu https://twitter.com/WOPR_Dev https://www.facebook.com/Adventures-in-NET-373059030062837/ https://twitter.com/dotNET_Podcast Picks Caleb Well: Paw Patrol On a Roll Wai Liu: Amazon Prime Video X-ray Feature
In this episode of Adventures in .NET the panel shares some of the things they have been doing in their work. Caleb Wells starts by talking about unit testing. His team at work started implementing unit testing he got to do a lot of research for their project. He shares some of the unit testing frameworks he looked at and explains why he chose XUnit. Other tools he is using include MOQ, Bogus and Fluent Assertions. They discuss what these do and how they make unit testing easier. Wai Liu tells Caleb all about GraphQL and why it is better than using a rest API. It is more efficient and cleaner. It is also easy to incorporate into an existing application. Wai also wants to discuss authentication. He explains that there is no need to create custom authentication solutions when there are so many great authentication tools built by people smarter than you. He recommends Firebase Auth by Google. The panel explains the difference between authentication and authorization. Panelists Wai Liu Caleb Wells Sponsors CacheFly ____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links GraphQL-dotnet NET Core 2: Why xUnit and not NUnit or MSTest https://xunit.net/ Quickstart Bogus Firebase Auth https://github.com/graphql-do tnet/graphql-dotnet https://fluentassertions.com/ https://www.ncrunch.net/ www.linkedin.com/in/wai-liu https://twitter.com/WOPR_Dev https://www.facebook.com/Adventures-in-NET-373059030062837/ https://twitter.com/dotNET_Podcast Picks Caleb Well: Paw Patrol On a Roll Wai Liu: Amazon Prime Video X-ray Feature
This week in the clubhouse, Stephen wants do more with less, Mark wants to do more with more, and Martha wants to do less to more."Because Internet: Understanding the New Rules of Language" - Gretchen McCulloch, book"Your conference is too damn big" - John Pavlus, Fast Company"The Game Design Studio on a Boat" - Clinton Nguyen, ViceEvil Games Club co-host Dale is now tweeting for us! Follow us for behind-the-microphone goodness: @nicegamesclub. We're always trying to get feedback, but it's hard! So Dale is encouraging gamedevs to start using #FeedbackFriday on Twitter as a way for to get opinions from their peers on things they're working on. Try it out this Friday! Extra Modes 0:07:06 Mark LaCroixProduction"Assassin's Creed Isn't Necessarily Done With Multiplayer" - Jordan Ramée, GameSpot"Why City Trial is the most memorable part of Kirby Air Ride" - Chris Hovermale, Destructoid"Fortnite Battle Royale Took Two Months to Develop and Launch" - Derek Nichols, GameRant"Riot got rid of League of Legends' URF mode because it made people stop playin… - Ali Jones, PCGamesN"Threading the Needle: The Making of Quake Team Fortress" - David Craddock, Shacknews"The making of Gwent" - Phil Savage, PC Gamer"Where Captain Toad: Treasure Tracker came from" - Michael McWhertor, Polygon Unit Testing 0:41:31 Martha MegarryProgramming"Unit testing with Jasmine: The very basics" - Aurel Kurtula, dev.toTesting Unity Projects - ilkinulas, GitHubNUnit framework"Unit Testing Tutorial: What is, Types, Tools, EXAMPLE" - Guru99, Guru99.com"What is Unit Testing, Why We Use It, and Sample Test Cases" - Lets Build That App, YouTubeTesting Computer Software, 2nd edition - Cem Kaner, book"The 100% code coverage problem" - Jeroen Mols
This week in the clubhouse, Stephen wants do more with less, Mark wants to do more with more, and Martha wants to do less to more. "Because Internet: Understanding the New Rules of Language" - Gretchen McCulloch , book "Your conference is too damn big" - John Pavlus , Fast Company "The Game Design Studio on a Boat" - Clinton Nguyen , Vice Evil Games Club co-host Dale is now tweeting for us! Follow us for behind-the-microphone goodness: @nicegamesclub We're always trying to get feedback, but it's hard! So Dale is encouraging gamedevs to start using #FeedbackFriday on Twitter as a way for to get opinions from their peers on things they're working on. Try it out this Friday! Extra Modes 0:07:06 Mark LaCroix Category Production "Assassin's Creed Isn't Necessarily Done With Multiplayer" - Jordan Ramée , Gamespot "Why City Trial is the most memorable part of Kirby Air Ride" - Chris Hovermale , Distructiod "Fortnite Battle Royale Took Two Months to Develop and Launch" - Derek Nichols , GameRant "Riot got rid of League of Legends’ URF mode because it made people stop playin… - Ali Jones , PCGamesN "Threading the Needle: The Making of Quake Team Fortress" - David Craddock , Shacknews "The making of Gwent" - Phil Savage , PC Gamer "Where Captain Toad: Treasure Tracker came from" - Michael McWhertor , Polygon Unit Testing 0:41:31 Martha Megarry Category Programming "Unit testing with Jasmine: The very basics" - Aurel Kurtula , dev.to Testing Unity Projects - ilkinulas , GitHub NUnit framework "Unit Testing Tutorial: What is, Types, Tools, EXAMPLE" - Guru99 , Guru99.com "What is Unit Testing, Why We Use It, and Sample Test Cases" - Lets Build That App , YouTube Testing Computer Software, 2nd edition - Cem Kaner , book "The 100% code coverage problem" - Jeroen Mols
Гости: - Рома Маринский - после Java, хлебнул вкус C# - Константин Горбачев - плотно сидит на C# - Алексей Каминский - любит C# всем сердцем Темы: - 00:05:16 - Плюсы и минусы автоматизации на Java, C#, .Net - 00:08:09 - Про плюсы .Net по сравнению с другими - 00:08:56 - Какие в C# / .NET есть инструменты, библиотеки аналогичные Selenide? - 00:09:41 - Про NSelene? - 00:11:22 - Проверенные продакшн проектами враперы для Selenium - 00:16:51 - JDI для C#? - 00:17:34 - Аналоги RestAssured для C# - 00:20:07 - Тест раннери для C#, паралелизация тестов - 00:20:50 - Про альтернативы Nunit раннеру - 00:23:50 - Решарпер + студия или Rider? - 00:31:52 - Определения уровня покрытия кода. Тулы в .net мире. Подходы. - 00:34:27 - Нагрузочное тестирование. Альтернатива Gatling на C# - 00:36:57 - Про контрактное тестирование - 00:38:37 - .Net/C# => Миграция с .Net Full на .Net Core - 00:46:14 - .Net/C# => .Net Core + Linux + Docker - 00:55:23 - Xamarin что там как? Лучше чем Appium? - 00:59:58 - Запуск Edge на С# с WebDriver - 01:01:12 - Про Selenium на C# - 01:01:49 - Библиотеки для сравнения изображений на C# - 01:03:16 - .Net/C# => Frameworks to mock/stub/fake external systems - 01:06:01 - GraphQL для автоматизации тестирования на С#. Есть ли готовые решения? - 01:06:48 - Параллелизация для Specflow - 01:09:48 - Про desktop автоматизацию - 01:17:32 - Про Ranorex - 01:25:49 - Можно ли спокойно жить если у тебя есть знания по Java, но компания рассматривает тебя как .Net автоматизатора? - 01:28:22 - Почему автоматизаторов на C# так сложно найти? - 01:36:50 - Open Source в .Net - 01:38:27 - Какие плюсы у автоматизации тестирования rest API на С#? а не Kotlin если сам проект на C#? - 01:44:35 - Патроны - 01:45:51 - Финал Telegram: t.me/automation_remarks Стать патроном: www.patreon.com/automation_remarks Спасибо патронам: Tetiana Hrybok, Marat Reymers, Nikita Verbitsky, Natalka Sokurenko, Ирина Юрчук, Valentin Buryakov, Roman Marinsky, Перетятько Игорь, Nikolay Georgievskiy, Serge Soloshchenko, Dmytro Pazykov, Katya Kravchenka, Igor Gruziev, Maryna Kolesnik, Dmytro, Alisa Markova, Vitaly Fedrunov, Roman Pobotin, Арина Аригри, Miguel Suddya, Maxim Denisov, Evgenii Gritcai
It's everyone's favorite topic... TESTING! That's right we tackle the world of unit testing, code coverage, user interface testing, acceptance testing, and so much more. Even though Frank and James are solo developers and there may not always be time to write a full suite of unit tests, that doesn't mean they don't dream of 100% code coverage. What does that even mean though? Does that mean your app will be flawless? Where do you get started and what should be your goals? We discuss on this week's show. Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Music : Amethyst Seer - Citrine by Adventureface Proudly recorded on Zencastr
It's everyone's favorite topic... TESTING! That's right we tackle the world of unit testing, code coverage, user interface testing, acceptance testing, and so much more. Even though Frank and James are solo developers and there may not always be time to write a full suite of unit tests, that doesn't mean they don't dream of 100% code coverage. What does that even mean though? Does that mean your app will be flawless? Where do you get started and what should be your goals? We discuss on this week's show. Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Music : Amethyst Seer - Citrine by Adventureface Proudly recorded on Zencastr
Carl and Richard talk to Hendrik Lösch about his experiences doing testing with Visual Studio 2012. Henrik starts out talking about unit testing, the different approaches with various tools, including mocking, moles and fakes. He talks about how MSTest has substantially improved in Studio 2012, but still needs help in the form of NUnit and/or xUnit.net. The conversation also digs into new generation tools like NCrunch and SpecFlow, rationalizing BDD, TDD and ATDD and ultimately dealing with the social challenges of making testing and quality a core part of your development experience.Support this podcast at — https://redcircle.com/net-rocks/donations
Andy Hunt is the author or co-author of several programming books including: The Pragmatic Programmer Programming Ruby (the Pickaxe book) Pragmatic Unit testing in C# with Nunit Practices of an Agile Developer Pragmatic Thinking and Learning: Refactor Your Wetware He's also one of the original signatories of the Agile Manifesto. Andy is a great person to talk about regarding Agile Development. Here are some things he says you need to become agile and where to start: Do a little of the right things all the time You'll be the expert on the project at the end of the project. Defer important decisions until you understand the problem. Stand up meetings Set ground rules Make sure you have a stable build environment and version control Unit Tests Continuous Integration Code Reviews/Pair Programming – Check the code Involve the Customer Produce something every 1-4 weeks Retrospectives – Get Feedback Download this Episode
Unit testing in C# can be performed with either the nUnit framework or the newly built in unit testing features of Visual Studio 2008. In this podcast you will see how to create unit tests for C# code using both of these tools.
Scott gets a rare chance to sit down in person with developers from three .NET Unit Testing Frameworks. Charlie Poole from NUnit, Jeff Brown from MbUnit, Brad Wilson from xUnit.NET as well as Roy Osherove, the author of the upcoming "Art of Unit Testing."
Guest: Gerard Meszaros Host: Martin Lippert Perhaps the greatest contribution of the agile methods community to software development has been the practice of automated unit testing: the writing of tests by programs that help to specify, document, and verify the code in our systems. Automated unit tests make possible other practices, such as refactoring and collective code ownership, and they help us to ensure a high-level of qaulity in our product. Tests are great, but we must keep in mind that they are code, too. The test suite grows over time, and without care we can run into the same sort of problems with our tests that we encounter in our code. Unlike production code, however, our tests sometimes feel optional, in that the team might think it can stop writing and maintaining tests when the perceived costs begin to exceed the perceived benefits. Gerard Meszaros, a developer and consultant with 25 years experience in software and a nearly a decade of experience in agile methods, wants to help teams avoid this calamity. He has documented his understanding of unit test suites in a comprehensive set of patterns for writing, monitoring, and maintaining test code. In this regard, Meszaros will teach an ooPSLA tutorial, titled Unit Test Patterns and Smells: Improving Test Code and Testability Through Refactoring. This tutorial, presented as a case study, teaches the best practices -- and "not so best practices" -- of unit testing as a set of patterns and as a set of smells for recognizing when the suite is going astray. Listen to this podcast to hear Martin Lippert of SE Radio talk with Gerard about unit testing, the Nunit family of automated test frameworks, and how to keep your test suites as clean and valuable to you as your production code.
Guest: Gerard Meszaros Host: Martin Lippert Perhaps the greatest contribution of the agile methods community to software development has been the practice of automated unit testing: the writing of tests by programs that help to specify, document, and verify the code in our systems. Automated unit tests make possible other practices, such as refactoring and collective code ownership, and they help us to ensure a high-level of qaulity in our product. Tests are great, but we must keep in mind that they are code, too. The test suite grows over time, and without care we can run into the same sort of problems with our tests that we encounter in our code. Unlike production code, however, our tests sometimes feel optional, in that the team might think it can stop writing and maintaining tests when the perceived costs begin to exceed the perceived benefits. Gerard Meszaros, a developer and consultant with 25 years experience in software and a nearly a decade of experience in agile methods, wants to help teams avoid this calamity. He has documented his understanding of unit test suites in a comprehensive set of patterns for writing, monitoring, and maintaining test code. In this regard, Meszaros will teach an ooPSLA tutorial, titled Unit Test Patterns and Smells: Improving Test Code and Testability Through Refactoring. This tutorial, presented as a case study, teaches the best practices -- and "not so best practices" -- of unit testing as a set of patterns and as a set of smells for recognizing when the suite is going astray. Listen to this podcast to hear Martin Lippert of SE Radio talk with Gerard about unit testing, the Nunit family of automated test frameworks, and how to keep your test suites as clean and valuable to you as your production code.
Carl and Richard talk to Hendrik Lösch about his experiences doing testing with Visual Studio 2012. Henrik starts out talking about unit testing, the different approaches with various tools, including mocking, moles and fakes. He talks about how MSTest has substantially improved in Studio 2012, but still needs help in the form of NUnit and/or xUnit.net. The conversation also digs into new generation tools like NCrunch and SpecFlow, rationalizing BDD, TDD and ATDD and ultimately dealing with the social challenges of making testing and quality a core part of your development experience.Support this podcast at — https://redcircle.com/net-rocks/donations