In this podcast episode, we discuss how testing is becoming more human-like across all levels, including API and Unit tests, driven by new tools that focus on real-world scenarios. We debunk the myth that design skills are innate, showing how they're rooted in science and can be learned like any other skill. Topics like color theory and psychological principles are highlighted for their role in enhancing developer skills. Finally, we examine the rapid growth of the low-code market, projecting that 65% of applications will use no-code solutions by 2024, leading to a significant shift in application development and management.

Stay updated with new weekly episodes every Thursday – and don't forget to subscribe! For more behind-the-scenes content, follow us @justshiftleft on Facebook, Instagram, Twitter, and LinkedIn.

in response to this tweet: https://twitter.com/Rovolutionary/status/1564338893691953154

Question about testing a reusable component

This interview was recorded for the GOTO Book Club.
http://gotopia.tech/bookclub

Roy Osherove - Author of "The Art of Unit Testing"
Dave Farley - Co-Author of "Continuous Delivery"

You can find more content like this on Dave’s "Continuous Delivery YouTube Channel": https://www.youtube.com/channel/UCCfqyGl3nq_V0bo64CjZh8g

DESCRIPTION
Good tests are crucial to any software project, and having a test-driven approach should be part of most projects’ goals nowadays. Yet testing can be difficult due to its complexity and challenges. Join a deep dive on how to approach unit testing with the author of “The Art of Unit Testing,” Roy Osherove, and a strong promoter of test-driven design, Dave Farley.
The interview is based on Roy's book "The Art of Unit Testing": https://bit.ly/3obiKNB

Read the full transcription of the interview here:
https://gotopia.tech/bookclub/episodes/getting-started-with-unit-testing

RECOMMENDED BOOKS
Roy Osherove • The Art of Unit Testing • https://bit.ly/3obiKNB
Roy Osherove • Elastic Leadership • https://amzn.to/3fxEgID
Roy Osherove • Notes to a Software Team Leader • https://amzn.to/3wjroxJ
Dave Farley & Jez Humble • Continuous Delivery • https://amzn.to/3ocIHwd
David Farley • Modern Software Engineering • https://amzn.to/3GI468M
David Farley • Continuous Delivery Pipelines • https://leanpub.com/cd-pipelines
Patterson, Grenny, Maxflied, McMillan & Switzler • Influencer: The Power to Change Anything • https://amzn.to/3hMGrdU

https://twitter.com/GOTOcon
https://www.linkedin.com/company/goto-
https://www.facebook.com/GOTOConferences

Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at https://gotopia.tech

SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.
https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

Twitter
Instagram
LinkedIn
Facebook

Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket: gotopia.tech

SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

We know, we know! It's been too long between episodes, but we had some speaking engagements, conferences, and general life going into November and here we are.

In this episode we cover unit testing, what it means to security vs what it means to engineers and some learning along the way as we dig into what makes a good unit test. All to often security engineers are telling development teams they need to write security unit tests, but they don't say how or what to write. We go through definitions, potential examples, and a bit of debate on this riveting nerd out of an episode of R2DSO.

We use RTL at work and I also use it for personal project. I understand what RTL is and what it isn't. My question is what are you using alongside RTL in terms of frontend testing? At work I'm pondering implementing Visual Regression testing on a large React application to cover things like unwanted CSS changes, but am also afraid of the overhead. Also, have you found any times that unit testing > RTL?

• Chromatic
• Storybook
• Percy.io
• Applitools
• The Testing Trophy and Testing Classifications

Libraries comparison: pros and cons of cypress Component Testing Library vs RTL

Cypress Testing Library

In this episode of Semaphore Uncut, Jon Reid, leading expert in unit testing and test-driven development (TDD) for iOS, talks about the importance of shaping production code in response to tests.

Jon is a Technical Agile Coach and the author of iOS Unit Testing by Example, XCTest Tips and Techniques Using Swift book.

Key takeaways:

• From Objective C to Swift
• Rapid test-driven development in iOS
• Fewer end-to-end, more unit-tests in iOS
• The real meaning behind the Testing Pyramid
• F-I-R-E: Understanding unit testing dependencies
• Test-Driven Development as a practice
• Bringing yourself to your code

About Semaphore Uncut
In each episode of Semaphore Uncut, we invite software industry professionals to discuss the impact they are making and what excites them about the emerging technologies.

Alex gives an introduction to unit-testing on iOS. He talks about what unit-testing is, how unit-tests are structured, and best practices on organizing your test code. He also touches upon mocking/stubbing and testing side effects as well.

Sign up for Alex's upcoming video course about iOS System Design Interview: https://iosinterviewguide.com/system-design-interview
Sign up for Alex's upcoming video course about RIBs Architecture: http://ribsarchitecture.com/video-course-waitlist
Need to prepare for an iOS Engineer Interview?
https://iosinterviewguide.com
Connect with us: https://twitter.com/insideiosdev
Email us at hello@insideiosdev.com

Materiały dodatkowe:

• xUnitPatterns Test Smells, lista Test Smells według Gerarda Meszarosa
• Software Unit Tests Smells, uzupełnienie listy o inne smelle i jedocześnie tool do ich wykrywania
• PIT Mutation Testing, testowanie mutacyjne w Java
• Infectionn PHP, testowanie mutacyjne w PHP
• Stryket.NET, testowanie mutacyjne w .NET
• Mutant, testowanie mutacyjne w Ruby
• Data i czas dla programistów, Michał Pipa, Boiling Frogs 2017, ciekawa prezentacja na temat "jak bardzo skomplikowany może być czas"

Because of the high complexity and depth of this episode, we will share with you the episode outline and the topics discussed here as a reference.

Episode Outline:

What is unit testing?

test for the smallest possible pieces of your program.

كل حاجة فيها سليمة بس لوحدها - سلطان السكري

Why Unit Testing

1. Help the developer deeper understand the logic he/she is implementing.
2. Help developer writes more modular, loosely coupled code.
3. Make it faster to develop and debug. (You can fake all the possible scenarios and see how the test is responding to each)
4. Find bugs early.
5. Help with documenting the code you are doing.
6. Help when it comes to refactoring.
7. It helps to automate the development process and decrease deployment-related friction.

Unit Testing Best Practices

1- Identifying Units:

When it comes to the unit you are testing, you need to answer three questions.

a. What is the output of this unit?

b. What helper functions that this unit is using to achieve that output?

c. Are there any side effects resulting from this unit. (it modifies state variables outside its scope).

2- Naming & Description

Why? it makes the test easier to read and hence easier to figure out what went wrong.

Describe & It. (This thing / should or does something)

- The search function should return an array of strings matching the search keyword.

- The search function should return an empty array when a keyword is not matching any.

- throw an exception if the keyword is an empty string.

3- Mocking & Stubs

- The unit test is 50% mocking and 50% clean code.

• Check Martin Fowler's article in the for more depth in mocking 

Check the resources section.

References:

• Martin Fowler's "Mocks Aren't Stubs".
• 8 Benefits of Unit Testing.
• The testing introduction I wish I had.
• Rethinking Unit Test Assertions.
• Unit Tests: More Readable Describe/It Statements in Protractor/Jasmine.
   

Episode Picks:

• Alfy: Dokkan Tech.
• Luay: Rich Dad, Poor Dad Book.

Key Takeaway: Even the most well developed SAAS solutions need extensive testing to avoid process errors, data breaches, failed integrations and operational issues when they go live.

Welcome to season two of the Underscore Transformation Podcast. We hope you enjoy this episode exploring the importance of comprehensive testing when rolling out a new system during your business transformation. This season focuses on the Build phase of transformation and follows on directly from season one (Scoping). If you haven't already, we recommend you listen to episodes 2-11 of season one as we will refer back to these topics, and they are vital in building the foundation knowledge required to move into the next phase of transformation.

Season two will cover the following points:  
1. Resource your programme team
2. Build your future support model
3. Manage business change
4. Solution design
5. Get the best out of suppliers
6. Target Operating Model – detailed design
7. Integrations & Reporting
8. Data
9. Testing, testing, testing
10. Governance & control

We will soon be releasing our white paper on the above points, which will be available for download via our website.

If you'd like to be notified of when this becomes available, please contact us via email, or register your interest via our website.

We’re always looking for ways to improve our content and would love to hear your feedback. If you would like to join the conversation, please contact Jason West to join our WhatsApp group.

Follow us on social media: @UnderscoreComms, find us on LinkedIn, or get in touch via email at enquiries@underscore-group.com

Visit our website to find more content on transformation, project resourcing, and talent development. 

This episode was recorded and produced by Matt Gore of icon business media.

Number one best practice: don't be dogmatic!

Stuff mentioned in this podcast:

• https://clubhouse.io
• 37signals Employee handbook.
• The Famous git flow article for git workflow.
• https://keepachangelog.com/ for changelog tracking.
• A good article for git mentioning git rebase, squashing .. etc.
• Gitlab ChatOps.
• Health Check Monitoring Tools.
  • Nightwatch: End-to-end testing, the easy way.
  • Elk stack.
  • LogRocket.
  • Sentry.
  • Prometheus.
  • Grafana.
• Planning Poker for estimation.
• Architectural decision records.
• Cypress for E2E testing.
• Lighthouse.
• Fastlane
• Today Picks:
  • Alfy: How to raise an adult book.
  • Luay: Business wars podcast.