Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are links to a tool that colorizes the text in the Log window. It's free and the source is in github so you can figure out how it works. The first link says that it just uses simple ANSI codes to do the job.</p> <p><a href="http://deepitpro.com/en/articles/XcodeColors/info" rel="nofollow">http://deepitpro.com/en/articles/XcodeColors/info</a><br> <a href="https://github.com/robbiehanson/XcodeColors#readme" rel="nofollow">https://github.com/robbiehanson/XcodeColors#readme</a></p> <p>To kick off the execution from within Xcode, you will probably need to add a new target to your project. To add a Target, click on your project and then there is an Add Target button on the bottom of the screen. I don't know exactly what you're executing but here are my best guesses based on your question:</p> <ul> <li>MacOSX/Application/Cocoa-AppleScript or Command Line Tool - Create a simple script or program that will execute your units tests.</li> <li>MacOSX/Other/External Build System - Allows for execution of an external "make" program with args.</li> </ul> <p>Once you have a way to execute your unit tests, you just need to figure out how to route the output from the unit tests to the Log window. If you can edit the Google Test project and make it use <code>NSLog()</code>, that would seem to be the easiest solution. You could create your own logging method, perform the ANSI colorization, and then send the final text to <code>NSLog()</code>.</p> <p><strong>ADDED</strong>: OK. Interesting findings... Read all before starting. Here's what to do:</p> <p>Start AppleScript Editor. This is in LaunchPad. Paste the following script into it:</p> <pre><code>tell application "Terminal" activate do script "&lt;your commands&gt;" in window 1 end tell </code></pre> <p>You can repeat the "do script" line as needed. Use this to execute your unit tests. In Script Editor, do Save As.../File Format=Script and save it to a safe location for now like your Documents directory. This will create a file like "UnitTests.scpt".</p> <p>Now go to your iOS project. Select the project at the top-left. Select the Build Phases tab top-middle. Click the Add Build Phase button on the bottom right. Here's the interesting part.</p> <p>Leave Shell as is ("/bin/sh"). Add one line:</p> <pre><code>osascript ~/Documents/UnitTests.scpt </code></pre> <p>That will execute the script after every build.</p> <p>But here's the interesting part I found. Click on Build Settings (top-middle). Make sure All is selected (not Basic). Scroll down the list to find Unit Testing. Open Test Host. Hit the + next to Debug. You can also put the above <code>osascript</code> command here. You might be able to execute your unit tests here and if you can, the output will likely show up in the Log! Let me know what happens.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I view the colorized output of Google Test in Xcode in the "All Output" window?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKent
    1. USKent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I view the colorized output of Google Test in Xcode in the "All Output" window?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI'd really rather not have to edit the Google Test code. That would imply that anything I want colorized would have to be rewritten to use `NSLog()` which, to me, is not feasible. Google Test is already outputting in color presumably using ANSI codes since it shows up in color in Terminal and on Windows in the console. I think I managed to route the output back into the output window (don't remember how unfortunately) but it wasn't in color. I had hoped XcodeColors would help solve that problem but as you mentioned, I think it has to go through `NSLog()` :(
      singulars
      1. PO
      1. USRotsiser Mho
    2. COIf you happen to know how to launch Terminal and run the tests (in color) when I hit "Run" the bounty is yours.
      singulars
      1. PO
      1. USRotsiser Mho
    3. COWorking on it, but this bounty expires in 1 hour (or less). This is approximately what the script will look like: tell application Terminal/activate/do script "exec tests here"/end tell.
      singulars
      1. PO
      1. USKent
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload