m-scott-lassiter / fred-the-developer Goto Github PK

As a user, I want to be able to see a comma separated list of which tests failed and which were inconclusive so I can more easily identify what I need to go fix in my unit testing.

As a user, I want to Assert conditions while I am unit testing so that I can verify my functions are returning the values I expect.

Unknown reason, it was working yesterday. Check the links. Possibly a relative link reference? File name extension problem? Does thie LICENSE file have to have a file extension?

As a developer, I want to be able to know when my unit tests were inconclusive, or even flag tests that I am still trying to write as inconclusive.

As a user, if I try to run dev.ModuleManager.Export and the dev.ModuleManager.Directory path address doesn't actually exist, I expect this to fail. Currently, it doesn't have any error handling that will prevent this which can lead to unexpected behavior.

As a developer, I want to be able to test that one value is greater than or equal to another while I am unit testing.

As a developer, I want to be able to test that two values are not equal while I am unit testing.

As a user, I don't want to have to manually set references in VBA because other people I distribute this project to that are not VBA developers will then not be able to use it or suffer unexpected errors they don't know how to handle.

FileScriptingObject is currently early bound, changing all references to make it late bound will fix this bug.

As an end user, I don't always want to install four different classes to use this product. For example, if I just want the logging features, I want to be able to have only the single class. Having all available Fred classes should enhance my workflows, not prevent me from using the individual portions.

The functionality in the ModuleManager class requires trusted access to the VBA project object model. This is the only step the end user will have to manually enable, so a graphical (GIF most useful) walkthrough showing how to find that setting and enable it will make her job a lot easier.

This is a very broad issue to track that the documentation is still heavily lacking. It will get closed when new issues are opened in more detail for the required sections.

As a developer, I want to be able to test that a value is false while I am unit testing.

As a developer, I want to be able to test that one value is less than or equal to another while I am unit testing.

Expected Behavior

When logging an event, I expect all log entries to have the same datetime format.

Current Behavior

Days and months <10 are formatted as a single digit (i.e. 8 instead of 08) which causes the log files to not align correctly over time.

Steps to Reproduce

1. Log an event before the 10th of any month
2. Log an event after the 10th of any month
3. Repeat for months January through September

Possible Solution

Change the private DateTime function to format Date as "MM/DD/YYYY".

Environment

Microsoft Office Version: Office 365
Program: VBA
Operating System: Windows 10
Other Relevant Information:

As a developer, I want to be able to see the results of all my unit tests.

To do this, I need to have properties for

• Number of Successes
• Number of Failures
• Number that were Inconclusive
• Report the results of this in either the Immediate window, an external log, or both
• Reset the test class to start again

Expected Behavior

After creating a new .xlsm file with this project and logging for the first time, I expect a new log file to get created with all appropriate headers.

Current Behavior

I made a new file, and the log entry got recorded correctly, but the log file has no header information.

Steps to Reproduce

1. Create a new .xlsm workbook
2. Add the fredDeveloper classes
3. Run this code, but replace the Events.LoggingFilePath with a new file path that doesn't exist:

Sub FredSourceControl()
    Dim Events As New fredDeveloper_Events
    Dim ModuleManager As New fredDeveloper_ModuleManager
    
    Events.Tic
    Events.LoggingFilePath = ThisWorkbook.Path & "\FredTheDeveloper_DebugLog.txt"
    Events.LoggingMode = ToImmediateAndExternal
    
    With ModuleManager
        .Directory = "C:\Users\mslas\Google Drive\LMD\Fred-the-Developer\Source Code"

        '.Export "fredDeveloper_Assert"
        '.Export "fredDeveloper_ClientSettings"
        .Export "fredDeveloper_Events"
        '.Export "fredDeveloper_ModuleManager"
        
    End With
    
    Events.Log ("All code modules exported. Run time: " & Events.Toc & " seconds.")
    
End Sub

Possible Solution

Investigate the CreateNewExternalDebugLogFile private method.

Environment

Microsoft Office Version: Office 365
Program: Excel
Operating System: Windows 10
Other Relevant Information:

As a developer, I want to be able to test that one value is less than another while I am unit testing.

Expected Behavior

When I try to import a class, I expect it to show up with the same name, and subsequent calls will reference the appropriate class, even if I am overwriting a class that was currently in use.

Current Behavior

When I tried to import "fredDeveloper_ModuleManager", it resulted in "fredDeveloper_ModuleManager1" and subsequent scripts thus didn't find the correct reference.

Steps to Reproduce

1. Run this script

Sub FredSourceControl()
    Dim ModuleManager As New fredDeveloper_ModuleManager
    
    With ModuleManager
        .Directory = ThisWorkbook.Path & "\Source Code"
        .Import "fredDeveloper_ModuleManager"
    End With

End Sub

2. Subsequent runs will not compile, because it overwrote fredDeveloper_ModuleManager as fredDeveloper_ModuleManager1

Possible Solution

Either prevent this behavior, or find a way to write as a second class, delete the first, and rename the second one.

Environment

Microsoft Office Version: 365
Program: Excel
Operating System: Windows 10
Other Relevant Information: None

As a developer, I want to be able to test that a value is true while I am unit testing.

As a developer, I want to be able to test that two values are equal while I am unit testing.

As a user, I would like a workbook that has the classes already in it along with some modules that demonstrate how the code works in action.

As a developer, I want to be able to test that one value is greater than another while I am unit testing.

Close after file is added and the main README is updated.