sketchup / testup-2 Goto Github PK

Allow for customized command syntax to fit each editor.

Add some knowledge of common editor to make it easier.

Sublime Text
https://www.sublimetext.com/docs/command-line
http://www.sublimetext.com/docs/2/osx_command_line.html

Notepad++
http://sourceforge.net/apps/mediawiki/notepad-plus/index.php?title=Command_Line_Switches

TextMate
http://manual.macromates.com/en/using_textmate_from_terminal.html

Visual Studio
http://stackoverflow.com/questions/350323/open-a-file-in-visual-studio-at-a-specific-line-number
devenv /edit myfile.rb /command "edit.goto 5"
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE

Xcode
http://stackoverflow.com/a/7973684/486990
xed --line 100 /Users/Anne/Desktop/Test/TestAppDelegate.m

VSCode
https://stackoverflow.com/a/64117773/486990
Code.exe --goto "C:\file path\filename.txt:450:11"
C:\Users\tthomas2\AppData\Local\Programs\Microsoft VS Code\Code.exe
-goto "{FILE}:{LINE}" --reuse-window

Create a runner that collects data required for displaying test results in the WebDialog UI.

Only TestUp window should handle bridge communications. The rest of the code should be blissfully unaware.

Indicate that a test that has previously been run is now removed.

Also add some function to clear removed tests.

Allow TC__.rb files to be wrapped in TC__ folder that can contain support files for the given tests.

When tests are discovered the metadata for only the active test suite is updated.

Add a button in WebDialog to refresh list of tests.
Should ideally keep existing run data.

Create a class for discovering tests. Should have an iterator method yielding the tests it find. That way it can be used to catch loading errors and display it in the UI.

Should each discoverer class be responsible per suite or testcase? Can per testcase allow multiple discoverers to be run in parallel?

Allow override of the name?

Currently using fam fam fam silk icons as placeholders.
http://www.famfamfam.com/

Before release, create new icons that fits properly with all sizes that the toolbar needs.

Add commands to build run failed tests, tests not run, tests passed.

Allow a summary of the tests be exported to some format.

SKUI disables text selection. This is not desired for the test results. It can be useful to copy and paste the messages.

Maybe alternatively have a Copy button/link to copy the test/testcase/testsuite results?

Just a reminder to test fully on both platform before releasing.

Sort test cases and test names as they are inserted.

Need to implement better function to convert test names to HTML IDs.

It adds a lot of noise. Is full backtrace needed? Or is it enough to be able to jump to the line of error?

It could be made into a always-folded field that needs to be expanded.

Maybe just for Errors - probably less need for Failures.

Make toolbar buttons be configuration toggles.

Add run control to WebDialog.

Run and visualize benchmarks.

Add an optional warning that can be enabled to get messages about use of old assert API that should ideally be updated to conform with the new framework.

When tests doesn't change it's good to have some visual confirmation the tests have run. Display a timestamp.

For persistent settings make a Settings class that abstracts Sketchup.read/write_default.

Add and configure the TaskbarProgress C Extension project for TestUp. Useful for displaying the progress of tests.

Implement compatibility asserts that Minitest removed in order to run our old tests.

Add an easy overview of total tests in suite as well as run, failed and error.

Traversing and loading files just to discover the test methods can be slow when all the tests for the Ruby API is processed.

Might want to cache the discoverer data. Track filename and filedate - only load when testcase has been updated.

When user clicks on test failure location it opens the file at given line position.
The editor needs to be able to be configured. Currently hard coded to Sublime Text.

Insert new tests in alphabetical order.

QA would like to automate the tests.

Add API methods to trigger tests without needing to open WebDialog or Ruby Console.

Output results to text file. Probably enough to use the default runner for this.

Example of current console runner output:

Can SKUI be included as a sub-repository?

For each testcase, append information about number of tests. Maybe also summarize how many have failed, after the title.

Or should number of fails etc, be seen only when expanding? Might make more sense - as a fail should auto-expand the testcase.

Needs to be considered how these are handled. And how they are ensure to not conflict with instance methods of the same name.

By default collapse test cases.

Loading/discovering testcases with identical names conflicts. Need to remove the test classes discovered and load the correct one when we run.

Currently the tests are not updated unless the windows is reopened or refreshed.

When a test fails, add a link that will open the file in user specified editor. Hopefully one can control which line it scrolls to.

I'd think that one could do this with Sublime Text - at the worst one has to write a small plugin - but that is ok.

There is no way TestUp2 can run side by side with old TestUp. But should there be a user friendly warning if someone have both installed?
Maybe someone have Developer Console installed...

The old TestUp had coverage overview based on a list of the Ruby API generated by ourdoc.rb. Now sure if that works any more, but such a tool might be nice.

I'd prefer to make this an XML/JSON manifest that is placed in the test suite folder.

Abstract the various UI components into smaller modules.

Allow user control over which tests to fold unfold.

The current structure isn't ideal. The responsibilities and names needs a cleanup.