#swifttesting — Public Fediverse posts

Parameterized test output in SwiftTesting can be opaque. Conforming to 𝐶𝑢𝑠𝑡𝑜𝑚𝑇𝑒𝑠𝑡𝑆𝑡𝑟𝑖𝑛𝑔𝐶𝑜𝑛𝑣𝑒𝑟𝑡𝑖𝑏𝑙𝑒 produces clear descriptions of exactly which parameters caused a failure.

🔗: https://craftingswift.dev/articles/improve-swifttesting-parameterized-tests-with-customteststringconvertible/ by Felipe Espinoza

#SwiftTesting #Testing #iOSDev

Parameterized test output in SwiftTesting can be opaque. Conforming to 𝐶𝑢𝑠𝑡𝑜𝑚𝑇𝑒𝑠𝑡𝑆𝑡𝑟𝑖𝑛𝑔𝐶𝑜𝑛𝑣𝑒𝑟𝑡𝑖𝑏𝑙𝑒 produces clear descriptions of exactly which parameters caused a failure.

🔗: https://craftingswift.dev/articles/improve-swifttesting-parameterized-tests-with-customteststringconvertible/ by Felipe Espinoza

#SwiftTesting #Testing #iOSDev

Parameterized test output in SwiftTesting can be opaque. Conforming to 𝐶𝑢𝑠𝑡𝑜𝑚𝑇𝑒𝑠𝑡𝑆𝑡𝑟𝑖𝑛𝑔𝐶𝑜𝑛𝑣𝑒𝑟𝑡𝑖𝑏𝑙𝑒 produces clear descriptions of exactly which parameters caused a failure.

🔗: https://craftingswift.dev/articles/improve-swifttesting-parameterized-tests-with-customteststringconvertible/ by Felipe Espinoza

#SwiftTesting #Testing #iOSDev

Parameterized test output in SwiftTesting can be opaque. Conforming to 𝐶𝑢𝑠𝑡𝑜𝑚𝑇𝑒𝑠𝑡𝑆𝑡𝑟𝑖𝑛𝑔𝐶𝑜𝑛𝑣𝑒𝑟𝑡𝑖𝑏𝑙𝑒 produces clear descriptions of exactly which parameters caused a failure.

🔗: https://craftingswift.dev/articles/improve-swifttesting-parameterized-tests-with-customteststringconvertible/ by Felipe Espinoza

#SwiftTesting #Testing #iOSDev

#buildInPublic #iosDev #coreData #swiftTesting

Since I’m eventually going to have to take a populated database and convert it from the old model to the new model, I’m going to tag the current repo so I can come back to it and build my test data. I should build a test database now that covers all the cases, but I am pretty sure that I’ll think of more as I go along.

Nevertheless, first order of business is to build some infrastructure to populate the test database.

2/n

#buildInPublic #iosDev #coreData #swiftTesting

Since I’m eventually going to have to take a populated database and convert it from the old model to the new model, I’m going to tag the current repo so I can come back to it and build my test data. I should build a test database now that covers all the cases, but I am pretty sure that I’ll think of more as I go along.

Nevertheless, first order of business is to build some infrastructure to populate the test database.

2/n

#buildInPublic #iosDev #coreData #swiftTesting

Since I’m eventually going to have to take a populated database and convert it from the old model to the new model, I’m going to tag the current repo so I can come back to it and build my test data. I should build a test database now that covers all the cases, but I am pretty sure that I’ll think of more as I go along.

Nevertheless, first order of business is to build some infrastructure to populate the test database.

2/n

#buildInPublic #iosDev #coreData #swiftTesting

Since I’m eventually going to have to take a populated database and convert it from the old model to the new model, I’m going to tag the current repo so I can come back to it and build my test data. I should build a test database now that covers all the cases, but I am pretty sure that I’ll think of more as I go along.

Nevertheless, first order of business is to build some infrastructure to populate the test database.

2/n

#buildInPublic #iosDev
Back to this after a hiatus of several weeks. Starting a new thread

previous thread is here https://mastodon.social/@Tom_frog/115686636425331266

I'm going to need to develop the alternate #coreData model described in the previous thread, then develop a data migration. Finally, I’ll need to sync and deduplicate. I will use the the #swiftTesting functions I added in the first phase to test the migration.

staying well away from AI since I want to actually understand what I’m doing at the end.

1/n

#buildInPublic #iosDev
Back to this after a hiatus of several weeks. Starting a new thread

previous thread is here https://mastodon.social/@Tom_frog/115686636425331266

I'm going to need to develop the alternate #coreData model described in the previous thread, then develop a data migration. Finally, I’ll need to sync and deduplicate. I will use the the #swiftTesting functions I added in the first phase to test the migration.

staying well away from AI since I want to actually understand what I’m doing at the end.

1/n

#buildInPublic #iosDev
Back to this after a hiatus of several weeks. Starting a new thread

previous thread is here https://mastodon.social/@Tom_frog/115686636425331266

I'm going to need to develop the alternate #coreData model described in the previous thread, then develop a data migration. Finally, I’ll need to sync and deduplicate. I will use the the #swiftTesting functions I added in the first phase to test the migration.

staying well away from AI since I want to actually understand what I’m doing at the end.

1/n

#buildInPublic #iosDev
Back to this after a hiatus of several weeks. Starting a new thread

previous thread is here https://mastodon.social/@Tom_frog/115686636425331266

I'm going to need to develop the alternate #coreData model described in the previous thread, then develop a data migration. Finally, I’ll need to sync and deduplicate. I will use the the #swiftTesting functions I added in the first phase to test the migration.

staying well away from AI since I want to actually understand what I’m doing at the end.

1/n