Testing Archives - IntelliTect

Integration Testing in Flutter: Part I

Joe Riddle — Thu, 29 Aug 2024 14:59:00 +0000

Here at IntelliTect, we love building mobile apps. We’re quite fond of frameworks like Flutter, Xamarin, and .NET MAUI that help developers create native mobile apps with a single codebase, helping you launch your next app into the app store faster. Building an app? Give us a call! I recently worked on an app using Flutter…

The post Integration Testing in Flutter: Part I appeared first on IntelliTect.

An Old Dog Learns a New TDD Trick

Tom — Fri, 25 Aug 2023 20:44:06 +0000

Do you think that Test Driven Development is worth it? It was for me! If you’ve been in the software development industry for a long time like me, you are faced with new methodologies, technologies, and other “ologies” that you are encouraged (or forced) to learn. You accept it because it’s part of the profession…

The post An Old Dog Learns a New TDD Trick appeared first on IntelliTect.

Shift Left with Type Hints in Python

Joe Riddle — Thu, 27 Apr 2023 17:40:57 +0000

Squashing Bugs Earlier and More Often with Python’s Type Hints Shifting left is the idea that you can reduce the cost of bugs by discovering and fixing (shifting) them earlier in the development process. Fixing a bug right after it’s written is far cheaper than after a pull request has been reviewed, merged, and deployed…

The post Shift Left with Type Hints in Python appeared first on IntelliTect.

Demystifying the SDET Unicorn

Mike — Wed, 22 Sep 2021 18:50:37 +0000

You Need an SDET Unicorn: Automation Engineers and Automated UI Tests Won’t Save You. I have a potentially controversial opinion about my job. The popular concept of the Software Development Engineer in Test (SDET) role is broken by modern development practices. I don’t say that lightly. After thirteen years in the industry and eight of…

The post Demystifying the SDET Unicorn appeared first on IntelliTect.

A Guide to Practical Unit Testing – Shift Left

Kevin Bost — Wed, 17 Feb 2021 20:42:22 +0000

Testing Early to Reduce the Cost of Bugs Testing is a topic that has been written about in-depth. It is well understood that bugs in software are very costly. Cost can be measured in many ways, but the key metric we will look at in this blog is time (developer time, testing time, support time, etc.). Over the years, many people have attempted to quantify the exact time-cost of a…

The post A Guide to Practical Unit Testing – Shift Left appeared first on IntelliTect.

Selenium: Attach to an Existing Chrome Browser with C#

Mike — Tue, 23 Jul 2019 17:17:03 +0000

Verifying with Selenium You’re testing a desktop application with Selenium. How do you verify an item on the page after the browser launches? I recently came up against this use case and couldn’t find a clear answer for C#. Every once in a great while, the need arises to have Selenium communicate to a browser…

The post Selenium: Attach to an Existing Chrome Browser with C# appeared first on IntelliTect.

Decoupling: Making Your C# Program More Testable

IntelliTect — Tue, 23 Apr 2019 18:55:51 +0000

How and Why to Implement Decoupling Classes in Your Code Estimated reading time: 9 minutes Decoupling is a strategy for writing testable code when dealing with hard-to-test classes, and it can be an incredibly powerful tool to help you write clean, effective, and bug-free code. Contents How and Why to Implement Decoupling Classes in Your…

The post Decoupling: Making Your C# Program More Testable appeared first on IntelliTect.

Painless Bug Testing through the Isolation of Variables

Mike — Sat, 09 Mar 2019 15:49:29 +0000

Why It’s Crucial to Catch Your Broken Functionality Before Sending it to Production QA resources waste time through long, protracted test efforts that try to hammer all of their bug testing through the UI at the end of (or after) development. One of the main problems with this approach is that it becomes tough to…

The post Painless Bug Testing through the Isolation of Variables appeared first on IntelliTect.

Deciding to Write a Wrapper

Mike — Tue, 10 Oct 2017 19:44:13 +0000

Wrappers Two things happened around the time I finished up writing a wrapper for Microsoft’s UITestControl class: I wondered if I should do the same thing for a web testing technology like Selenium, and I discovered that at least some discussions exist on if wrappers could be considered an antipattern. As I began to investigate…

The post Deciding to Write a Wrapper appeared first on IntelliTect.

Unit Testing With Xamarin Forms

IntelliTect — Tue, 30 May 2017 16:40:42 +0000

Exploring Xamarin Forms In a recent application that IntelliTect developed for a client, we were tasked with building a Xamarin forms application that supported Windows, Android, and iOS. Due to the cross-platform support inherent with using Xamarin, a large majority of our code was common amongst all three implementations. As with most cross-platform projects, however,…

The post Unit Testing With Xamarin Forms appeared first on IntelliTect.

The Feasibility of Test Automation

Mike — Fri, 26 May 2017 22:00:47 +0000

Test Automation With proper tools, technical approaches, and processes, automated testing improves software quality, time to market, and reduces overall costs. Starting early in the development process and maintaining a pragmatic approach will maximize chances of success. However, there is no “one size fits all” approach; proper approaches vary based on team resources and project…

The post The Feasibility of Test Automation appeared first on IntelliTect.

Making Unit Testing Easier

Kevin Bost — Thu, 04 Aug 2016 19:28:17 +0000

Simplifying Unit Tests I love unit tests. Specifically, I love unit tests that are easy to maintain. When I spend more time setting up a test then doing actual testing, it is a very strong code smell. Sloppy unmaintainable code has no place in your projects, especially not in your unit test project. In…

The post Making Unit Testing Easier appeared first on IntelliTect.

Part 2: Scrum From a QA Perspective

Mike — Thu, 17 Dec 2015 00:52:11 +0000

Analyzing Scrum Part 2: There is an excellent blog that describes software development as engineering a bridge: Imagine joining an engineering team. You’re excited and full of ideas, probably just out of school and a world of clean, beautiful designs, awe-inspiring in their aesthetic unity of purpose, economy, and strength. You start by meeting Mary,…

The post Part 2: Scrum From a QA Perspective appeared first on IntelliTect.

Improving Unit Tests With AutoMocker

Kevin Bost — Fri, 02 Oct 2015 17:27:48 +0000

Further Discussion on Improving Unit Tests With AutoMocker In my previous post, I presented an example of using mock objects to improve unit testing. In this post, I would like to expand upon my previous example to make the tests more robust in order to handle signature changes to the ViewModel’s constructor. First, we will…

The post Improving Unit Tests With AutoMocker appeared first on IntelliTect.

Unit Testing With Mocks

Kevin Bost — Thu, 10 Sep 2015 22:37:23 +0000

Exploring Unit Testing in C# Unit testing is an integral part of the development process. However, when a class has several dependencies it can be tiring and cumbersome to create mock implementations for all of them. Leveraging a mocking library can save large amounts of time and make for better unit tests. Though there are…

The post Unit Testing With Mocks appeared first on IntelliTect.

Part 1: Scrum From a QA Perspective

Mike — Thu, 06 Aug 2015 17:49:22 +0000

Fulfilling the Role of a QA Engineer I work QA but am not solely on a QA team; I am a member of a Scrum team. Like the other members, this means I am a part of the development team, I just happen to specialize in QA practices. This is the first position at which…

The post Part 1: Scrum From a QA Perspective appeared first on IntelliTect.

Relative Paths for Visual Studio Generic Tests

Mark Michaelis — Mon, 21 Oct 2013 02:26:38 +0000

Creating a Generic Test To make generic tests robust enough to run for all developers on your team and on the build server, you are likely going to want to avoid hard coding the path to the executable. To do this successfully, you need to have a list of all the environment variables that are…

The post Relative Paths for Visual Studio Generic Tests appeared first on IntelliTect.

Why to Not Use the System Diagnostics Assert Methods

Mark Michaelis — Sat, 22 Oct 2005 23:53:52 +0000

Do Not Use the System Diagnostics Assert Methods Unless… Assertions should never appear in release code. Assertions are a debug mechanism for revealing bugs within code during development. Failed assertions in release code indicate the bug was missed and allow the option of debugging at the assertion location. However, end users should not be presented…

The post Why to Not Use the System Diagnostics Assert Methods appeared first on IntelliTect.

Unit Testing Input & Output

Mark Michaelis — Thu, 13 Jan 2005 00:26:51 +0000

Creating An Attribute for Redirecting Console Input & Output While writing my Essential C# (Addison-Wesley), I created many console applications. Unit testing has been rather cumbersome. I decided to create an attribute that can redirect the console input and output so that I can supply various inputs and then test the output. I went with…

The post Unit Testing Input & Output appeared first on IntelliTect.