I remember going to the theater over the Thanksgiving holiday in 1987 and seeing Planes, Trains, and Automobiles with Steve Martin and John Candy. My family didn’t often take in the holiday weekend movie releases, but Steve was a family favorite actor already, and friends had given it a good review. Having watched it just […]
2024-07-20
226 reads
When and where should you test code? Steve has a few thoughts when we consider the database as a crucial part of our software.
2024-06-26
205 reads
With Flyway, you can adopt a test-driven development strategy that will allow you to test and evaluate databases, and database objects, at every phase of the database development lifecycle. The further down the delivery pipeline that bugs appear, the more costly in time and resources they are to fix. This approach will allow you to catch many of them before the database change even gets committed to version control, making a continuous delivery process much easier to adopt and sustain.
2024-02-12
A software bug causes a lot of legal issues in the UK. It's something that upsets Steve, partially because the software wasn't well tested.
2024-02-05
264 reads
Most applications have large and complex databases at the back end, making it hard for developers to adequately test their work before it goes out. Having a fast, repeatable process to deliver data on demand is an essential part of an effective software development lifecycle, ultimately leading to improved customer satisfaction. In this article, we’ll explore the journey our own engineering team went on to leverage our own tool, Redgate Clone, to spin up short-lived database instances in containers for automated testing.
2023-10-25
In this tip, we will discuss the process of generating test data to verify query logic without relying on real-life data, along with some helpful guidelines. We will also cover various scenarios and their corresponding solutions.
2023-09-15
A term I have only recently learned is "shift left testing." You can read more about this on Wikipedia here. The term was coined in 2001 and generally means testing earlier in the development lifecycle. Hence, shifting your testing left in the timeline. Just how left should you shift your testing, though? In my mind, so early, the rooster hasn't entirely fallen asleep yet.
2023-03-01
Automated testing is a way to ensure you can repeatedly examine your code as you make changes by running a series of tests. Since these are automated, you have the ability to execute all tests with one programmatic call rather than hoping a developer runs all tests. This also allows the effort of writing tests […]
2023-10-15 (first published: 2023-02-22)
1,140 reads
Crowdsourcing is one way to get a job done. In this article, Devyani Borade describes crowdsourcing quality testing of software.
2022-01-26
2020-02-17
202 reads
By James Serra
Making Data AI-Ready, Part 3 (This is the final article in a three-part series...
By Steve Jones
I use ConEmu for my terminal interface. I’m still on Windows 10 at home,...
Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built...
WhatsApp Cs 628218520153 Gedung Grand Indonesia Mall A, Lower Ground No. 20-21, Jl. M.H....
WhatsApp Cs 628218520153 Pusat Grosir Senen Jaya Blok A8-9, Lantai 2, RW.3, Senen, Kec....
WhatsApp Cs 628218520153 Jl. P Jayakarta Komp. No.127, RT.7/RW.7, Mangga Dua Sel., Kecamatan Sawah...
Which number did the two COUNT(*) return:
DROP TABLE IF EXISTS #tmp CREATE TABLE #tmp (id INT NOT NULL) INSERT INTO #tmp (id) SELECT gs.value FROM GENERATE_SERIES(1, 5) AS gs ALTER TABLE #tmp ADD my_value INT NOT NULL CONSTRAINT df_tmp_my_value DEFAULT 1 SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1 ALTER TABLE #tmp DROP CONSTRAINT df_tmp_my_value ALTER TABLE #tmp ADD CONSTRAINT df_tmp_my_value DEFAULT 2 FOR my_value SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1See possible answers