<sarcasm> It is really nice that Apple tells us that the accessibility identifier is DEPRECATED - What The F....? it looks like a button... can I click and find out WHY? and what I should use moving forward?.... NO! Son Of A Bitch.

This would be a really good place for documentation - Apple!?!

"Does it blend?" comes from the YouTube - Will It Blend? and the host Tom (he's from the future).

That's what I wanted to do with Xcode - press the John Conor button on the blender.

Testing with XCUI show...

What did we learn since then - that no one really knows the secrets to getting Xcode to work with the accessability identifiers that you might sprinkel into your source...

Here are two different articles - each suggesting the use of the SwiftUI element accessibilityIdentifier but with different advice/code to retreive the element inside the testing code:

1) app.staticTexts["my_ID"]

2) app.otherElements["my_ID"]

For the implementation code:

someView.accessibilityIdentifier = "my_ID"

Now one could easily test the test code to see which works...

Except for when neither instance works.... like in the SwiftUI TabView.

This is the type of situation that a company with as much money in the bank as Apple has; they could spend a bit (just a tiny portion) and hire a few technical writers to put some words in their tooling's documentation.

https://www.twitch.tv/videos/887620828

Testing clean up … in review we had some test that didn’t follow our REF ARCH idea of:

func test_methodUnderTest_secnarioDescribedDAMPly

Wonder how much code we are writing and how well we are doing with our Test?

Baseball Model 5 swift files & 5 test files with about 90 Asserts but about 700 lines of implementation code with about 700 lines of testing code.

Ol-skool method of counting lines of code:

unix> find . -name "*.swift" -print0 | xargs -0 wc -l

Mac:Model david$ find . -name "*.swift" -print0 | xargs -0 wc -l

96 ./Play.swift

437 ./Game.swift

73 ./Inning.swift

86 ./Player.swift

41 ./LineUp.swift

733 total

Mac:Model david$

Mac:Baseball-Tests david$ find . -name "*.swift" -print0 | xargs -0 wc -l

57 ./LineUpTest.swift

208 ./PlayTest.swift

237 ./GameTest.swift

33 ./PlayerTest.swift

120 ./InningTest.swift

655 total

Mac:Baseball-Tests david$

Wonder if there’s a Xcode tool that can help with this type of assessment?

A Code Coverage tool? Hmmm…

Also - a Editor > MiniMap will help with the Game.swift file that has grown so big…

https://www.twitch.tv/videos/872742181?filter=highlights&sort=time

ToDo:

• LineUp is a RingBuffer - that does NOT cycle like I want.

Here is the code we found on the net... Ring Buffer on GitHub Swift Algorithm Club. Let's rwrite our own LineUp class. It will allow the reading of the next batter to cycle around and around (thru the 9 players in the game).

Note: automatic advancement of runners on base - now the order of calls to advance runners matters.

Counting of score (Visitor vs Home)

Adding other atBat types…

Move Play method runnerOn(base, action) into Game class.

Game needs a factory method for Innings (much like Play)

https://www.twitch.tv/videos/867345318?filter=highlights&sort=time

Refactoring Play init.

Recognizing the poor Play() initialization with an outcome; removed the AtBat from the init()

Which rippled thru all test….

Created a method Play.called(AtBat) // umpires call each play

Refactoring all classes to have “default” Access Level (not Public)

Pushed to GitHub

Play object is needing to keep track of the runners on base - the game situation

So the new called() method will be responsible for putting batter’s on base

Yet what moves the runners - they should move before the batter.

GREEN - do I refactor issues above?

Options:

• 1) make Game the owner of bases and base info (NOT a Refactoring)

  • • 1. • Move enums into Game (from Play)

         • Copy runnerOutcomes into Game

         • Make a nextBatter() factory for Play

         • Split RunnerOutcomes - move Bases into Game

         • Rename runnerAdvances to runnerOn(base, action)

         • runnerOutcomes - need each base line (4)

• 2) player == method (Close to Refactoring) >> now use it!

• 5) move EmptyPlayer to Player file

• 9) runnerOutcomes are strings - make them RunnerAction type

• 10) move Game-runnerActions to Play

• 3) baseOutcomes are strings… move into Game (NOT Refactoring)

• 4) Play needs access to Game - maybe Game is a Play Factory (NOT Refactor)

• 12) new init() for Play that allows an AtBat for static init. - capability for real data in view.

• 13) whichInning() whichHalf() methods

• 14) change Inning.number : String to be named label.

• 11) when Plays are created they should be appended to an Inning

• 6) add another play type (new Test) - bases loaded and a WALK should Score Run.

• 8) unit test RingBuffer (found on Net) used for lineUp in Game

  • • 15) RingBuffer read didn’t wrap around on 10th read. << FIXME

In doing all of this above - I lost the static rich data of AtBat records that the running example game used on screen…. To get back that info of AtBat - added another init() method that takes the AtBat outcome of Play class. Now the display canvas & example App have data that is rich and shows the AtBat info.

Some of my favorite videos on Swift and good developer practices.

Great Developer Habits - WWDC 2019