Anthony

Cadence Report

Date: Mar 21 - Mar 27

Work Done:

Looked into graphics/UI and import statements.

Difficulties:

Errors/not handled statements are hard to notice when running test files.

Learned:

Import statements cause "error: no such module" errors.

Next Week:

Look into adding arguments to allow for import statements

Cadence Report

Date: Mar 14 - Mar 20

Work Done:

Submitted pull request for lucid dreams test files. Changed my swiftc symlink to point to the one in the ninja build directory. Started looking into test case results.

Next Week:

Create a report of test cases and their results/ errors

Cadence Report

Date: Mar 7 - Mar 13

Work Done:

Added lucid dream test files to github Reviewed bash commands and scripts.

Difficulties:

Unsure what to look for when running tests with ./swiftc

Learned:

How to run through all files in a directory with bash

Next Week:

Pull request. Link swiftc to ninja build directory. List of errors.

Cadence Report

Date: Feb 28 - Mar 6

Work Done:

Generated output from lucid dreams test files

Difficulties:

Was unsure about how to actually test the files

Learned:

Why and how to use symlink All the previous lucid dreams test files are on the server so I didn't need to download them and do everything locally.

Next Week:

Bash file to automatically run through the tests and generate outputs Analyze the generated output files.

Cadence Report

Date: Feb 20 - Feb 27

Work Done:

Created testcases for sets and subtracting function. Looked at the graphics files in lucid dreams

Learned:

Sets are unordered collections. Since they are unordered, when they are printed out, the order varies each time.

Next Week:

Graphics tests? (CoreGraphics and/or UIKit)

Cadence Report

Date: Feb 7 - Feb 13

Work Done:

• Renamed previous test cases
• Looked into swift testcases located at https://github.com/apple/swift/tree/master/test/

Difficulties:

• Not sure how the tests will be executed, should we have a driver program?

Learned:

• Almost all swift testcases don't print anything, they just execute what they're testing

Next Week:

• Write more test cases
• Replace print statements in tests with comments?

Cadence Report

Date: Jan 31 - Feb 6

Work Done:

• Created test cases for logical AND and logical OR
• Created test cases for substring methods (including to: and from: usage)
• Created uppercased test

Difficulties:

Learned:

• Running swift from the terminal is very easy, simply type swift and then you can put in any swift commands that you wish
• Given a series of logical ANDs, swift will process it left to right and stop evaluating after the first false
• Similarly with logical ORs, swift will stop the evaluation after the first true (short circuit evaluation)

Next Week:

• Look through the Dream+Diff.swift file and create more test cases
• Understand how "\(self)" works in swift
• Organize test cases somehow

Cadence Report

Date: Jan 23 - 30

Work Done:

• Read the testcases already made for LucidDreams
• Looked through the model folder of LucidDreams and found syntax/functions that weren't already covered by the previous test suite

Difficulties:

• The previous test suite seemed a little out of order compared to the Dream.swift file.

Learned:

• There are many different things you can do in Swift. There are often many different ways to do the same thing(or similar) but they all should be tested. ex. a = a + 1 a += 1

Next Week:

• Create test cases to cover the missing cases that I found in the previous test suite