StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7717585
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-10T19:24:30.013
FavoriteCount
0
LastActivityDate
2011-10-11T16:34:36.050
LastEditDate
2011-10-11T16:34:36.050
LastEditorUserId
636733
OwnerUserId
636733
ParentId
7654729
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I've finally figured out how to make the verifications and assertions get reported in a useful format for my needs. The problem is that the default structure of the tests when simply exporting a Selenium IDE recorded script into a Python RC file lacks a lot of detail I needed. What I changed: - Placed the Selenium start and stop methods in the Setup and tearDown classes which prevented Selenium from restarting the browser with each newly defined verification/assertion method - Added error descriptions that include the testcase name via inspect.stack() <hr> <pre><code>import inspect, unittest, xmlrunner from selenium import selenium class TESTVerifications(unittest.TestCase): @classmethod def setUpClass(self): self.selenium = selenium("localhost", 4444, "*iexplore", "https://workflowy.com/") self.selenium.start() self.selenium.set_timeout("60000") print("setUpClass") self.selenium.window_maximize() self.selenium.open("/") def setUp(self): self.verificationErrors = [] def test_verification1_error(self): try: self.assertEqual("This application is designed", "This application is designedZZZZ",(inspect.stack()[0][3]) +" text missing 'This application is designed'") except AssertionError, e: self.verificationErrors.append(str(e)) def test_verification2_error_two_times(self): sel = self.selenium ##No such element exception try: self.assertEqual("First failure", "First failureZZZZ",(inspect.stack()[0][3]) +" First failure'") except AssertionError, e: self.verificationErrors.append(str(e)) try: self.assertEqual("Second Failure", "Second FailureZZZZ",(inspect.stack()[0][3]) +" Second failure'") except AssertionError, e: self.verificationErrors.append(str(e)) def tearDown(self): #self.selenium.stop() self.assertEqual([], self.verificationErrors,"Results: " + str(self.verificationErrors)) @classmethod def tearDownClass(self): self.selenium.stop() print("tearDownClass") if __name__ == "__main__": # unittest.main() unittest.main(testRunner=xmlrunner.XMLTestRunner(output='test-reports')) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSelenium syntax for Verifications that work with Hudson / jenkins
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USgorbysbm
UserOwnerUserId
1. USgorbysbm
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSelenium syntax for Verifications that work with Hudson / jenkins
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.