Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>On my GAE project, I use:</p> <ul> <li><a href="http://code.google.com/p/nose-gae/" rel="noreferrer">NoseGAE</a>&mdash;This is the critical piece that ties all the rest together</li> <li>Mock, as in John's excellent answer. I use this largely for AWS and other web services</li> <li>Fixtures (the package, not the idea)</li> </ul> <p>I also prefer many of Rails's idioms. I broke my tests into unit, and functional using Python packages. You can run a subset of tests using <code>--tests=unit</code> or <code>--tests=functional</code>. It is all a bit more manual than Rails but at least I can unit test the hard stuff and make sure I never have regressions.</p> <p>I also made a simple <code>FunctionalTest</code> class to do much of the very common actions in Rails, such as <code>assert_response</code> and <code>assert_xpath</code> (similar to assert_select).</p> <pre><code>class FunctionalTest(Test): def get(self, *args, **kw): self.response = app.get(*args, **kw) def post(self, *args, **kw): self.response = app.post(*args, **kw) def assert_response(self, expected): pattern = str(expected) if re.search(r'^\d+$', expected) \ else (r'^\d+ %s' % expected) assert re.search(pattern, self.response.status, re.IGNORECASE), \ 'Response status was not "%s": %s' % (expected, self.response.status) def assert_xpath(self, path, expected): element = ElementTree.fromstring(self.response.body) found_nodes = element.findall('.' + path) if type(expected) is int: assert_equal(expected, len(found_nodes)) elif type(expected) is str or type(expected) is unicode: assert (True in [(node.text == expected) for node in found_nodes]) else: raise Exception, "Unknown expected value: %r" % type(expected) </code></pre> <p>If you are doing lots of ListElement equality searches, definitely learn the <code>--tests=foo</code> syntax because testing for matching elements within a list is very slow.</p> <p>Sometimes I like to load the Rails console against my fixture data to see what's going on in the test environment (i.e. <code>script/console test</code>). To do something similar with GAE, run dev_appserver.py with the parameter <code>--datastore_path="$TMPDIR/nosegae.datastore"</code> (or possibly substitute <code>/tmp</code> for <code>$TMPDIR</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I go about setting up a TDD development process with Google App Engine?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJasonSmith
    1. USJasonSmith
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I go about setting up a TDD development process with Google App Engine?
      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. VTUpMod
    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. VTUpMod
    1. COAccepted this answer for the critical NoseGAE bit of information, though John's answer was incredibly helpful as well.
      singulars
      1. PO
      1. USBob Aman
    2. COThanks, Bob! Indeed, I plan to integrate more of John's suggestions into my own projects in the future.
      singulars
      1. PO
      1. USJasonSmith
    3. COBob, going back through my code I noticed that I had a way to run the normal SDK server against the NoseGAE-created data store, so I added that as the last paragraph.
      singulars
      1. PO
      1. USJasonSmith
 

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