1: $time = Get-Date;

   2: 

   3: ##Show Minutes

   4: $time.Minutes;

   5: 

   6: ##Show Day

   7: $time.Day;

   8: 

   9: ##Find out NOW stuff

  10: (Get-Date).Day;

  11: (Get-Date).Millisecond;

  12:  

  13: ##What Will the Date be 90 days from now?

  14: (Get-Date).AddDays(90);

  15: 

  16: ##What was the day 90 days ago?

  17: (Get-Date).AddDays(-90);

  18: 

  19: ## And for something practical

  20: $startTime = Get-Date;

  21: $endTime = Get-Date;

  22: "DONE in less than " + ($endTime.AddMinutes(1) - $startTime).Minutes + " Minutes";

As you can see, wonderfully simple.

• Enough facts to give the delivery team (Dev , QA, DBAs, Operations, etc.) a direction
• Enough proper estimation to allow the product owner to know when he might expect delivery of the story
• Enough detail to know when the team has completed the story.

We should all be familiar with the “As a [role], I can [feature] so that [reason]” format of writing a story (quote swiped from codesqueeze.com).  And we should all be familiar with Ron Jeffries’ 3 C’s (Card, conversation, and confirmation).  The thing that gets lost most often, I think is that second C. 

So I have two anecdotes for you to demonstrate the value of “conversation”.  (I’d call them stories, but that would just get confusing).  For the purposes of these anecdotes, the delivery team is represented by the store clerk and the product owner/manager is represented by the customer.

Anecdote #1:

Joe Customer goes into the EverythingMart where they sell absolutely everything (as the name implies) and finds Steve Storeclerk. 

“Hey there Steve!  I’m back again and I need something from you!”

“Sure,” Steve replies, “How can I help?”

Joe Customer rubs the back of his neck with a well worn handkerchief and says, “Well, I need to haul some stuff, so I need to buy a truck from you!”

Steve’s enthusiastic to help so he pulls up the catalog of trucks on his terminal, “Perfect, we’re getting some new ones in a couple weeks!  Why don’t we sit down and take a look at what will work for you.”

“Two weeks, eh?” Mr. Customer asks, “Well, alright, I suppose so. Let’s see what you’ve got.”

The pair of them look through the catalog and pick out a blue one with chrome bumpers, GPS, and a gun rack (they live in TX and it’s a free option, so why not?).

A week Joe Customer comes in with his check for $30,000 and drives his truck home and does his hauling.  Everyone seems happy.

Now, as a “Story” we could write this on a card as …

“As a customer, I can haul heavy things, so that I don’t kill my back.”

Seems to meet all the criteria for a good story, right?

Anecdote #2:

Joe Customer goes into the EverythingMart where they sell absolutely everything (as the name implies) and finds Steve Storeclerk.

“Hey there Steve! I’m back again and I need something from you!”

“Sure,” Steve replies, “How can I help?”

Joe Customer rubs the back of his neck with a well worn handkerchief and says, “Well, I need to haul some stuff, so I need to buy a truck from you!”

“Of course, I’m sure I can help you out.  What exactly do you need to haul?” Steve asked.

“Ummm…  I’ve got some bricks that I need to bring over to my neighbor’s house to help him build a barbecue.”

Steve nods sagely and asks, “Right… And how far do you gotta haul these bricks?”

“Just two houses down,” he’s told.

Steve then logs onto his workstation and starts to browse around looking at gardening implements.  “I think one of these wheel-barrows will do just fine.  And we have them in stock right now.”

Joe Customer’s eyebrows arch inquisitively. “So,” he asks, “you don’t think that I need a truck, but this wheel-barrow will do?”

“Absolutely!” Steve tells him.  “And this will save you a bundle!”

Joe nods, whips out his credit card and pays $50 for a brand new shiny wheel-barrow.  Sure, it’s going to take him two trips to get all the bricks moved, but he’s still going to be finished by the end of the day.

Now as a “Story” we could write this on a card as …

“As a customer, I can haul a load of bricks to my neighbor’s house, so that I don’t kill my back.”

Sure, the first story seemed well defined, the customer told Steve exactly what he wanted and got what he wanted, albeit at a pretty heavy cost in terms of $ and time.

In the second story, though, with conversation Joe Customer got what he needed immediately and at a substantially lessened financial burden.

We should never assume that the customer knows exactly what they need.  Instead of dictating a solution, conversation allows us to solve the need.

To paraphrase a Rolling Stones song…

“You can’t always get what you want (at a decent cost). But if you have a conversation, you just might find, you get what you need.”

Please add the directory containing ''firefox.exe'' to your PATH environment variable, or explicitly specify a path to Firefox 3 like this:
*firefox3c:\blah\firefox.exe on session null

That proved frustrating as well.  However, the addition of a simple space proved to be the key.

My setUp() method now looks like this ( of course this is hardcoding firefox.  I haven’t gone in and cleaned that up yet):

   1:  @BeforeClass(  )

   2:  @Parameters({"browser", "seleniumGridIp", "seleniumGridPort", "testServer", "testEnv" })

   3:  public void setUp( String browser, String seleniumGridIp,

   4:          int seleniumGridPort, String testServer, String testEnv) throws Exception {

   5:          

   6:          browser = "*firefox C:\\Program Files (x86)\\Mozilla Firefox\\firefox.exe";

   7:          sel = new DefaultSelenium(     seleniumGridIp,

   8:                  seleniumGridPort,

   9:                  browser,

  10:                  testServer);

  11:   

  12:          sel.start();

  13:          sel.open(testServer);

  14:   

  15:      }

I hope this helps someone.   It’s not an ideal solution…. but it works.

Cedric Beust (the guy who wrote the book on TestNG) added a comment with a way to run single tests much much easier.  Go check out the comment below.  I'm going to leave this article up, though, I think that people might find the examples of parameters and groups might still prove useful.

----------------------------------

It's a typical story.  You have all of your tests written up with Selenium and everything is working beautifully.  Then you discover the beauty of TestNG's ability to run the tests in parallel. By adding some parameters to the XML, you are able to run multiple copies of the same tests on different browsers and operating systems. The clouds part, the angels sing on high, and you find your boss showering you with praise for cutting the total run time from four hours down to fifteen minutes.

But all is not as good as you thought.  Those blasted developers decided to change something on the page and one of your two hundred thirty-four tests is now broken. So, you dutifully open Eclipse and begin the repair work.  You finish adjusting your assertions, right-click on your test method and choose to "run as TestNG test."

Despair!  Anguish!! Gnashing of teeth!!! I don't want to run my entire class of tests just to debug a single test!!

"What the hell does that mean?"  you ask as you stare at the console output, which tells you ...

org.testng.TestNGException:
Parameter 'browser' is required by @Configuration on method setUp
but has not been marked @Optional or defined in C:\<MyUserDir>\AppData\Local\Temp\testng-eclipse--1466657283\testng-customsuite.xml
    at org.testng.internal.Parameters.createParameters(Parameters.java:144)
    at org.testng.internal.Parameters.createParameters(Parameters.java:327) ...

Apparently, when you attempt to run a single test, you are never asked to point Eclipse at the XML file you wanted to use.  Eclipse and TestNG create a nice temporary one just for the occasion.  Unfortunately, there is no way to tell the IDE where to get any XML information from.

After much cursing, scouring Google, and complaining to my co-workers, I have devised a method that allows me to run any single test (or combination of tests) without having to run the entire class' list of tests.

Here's how ...

Create an XML file for your own debugging purposes. 
You probably want to use all of your typical parameters like browser type, location of the Selenium Server/Grid Hub that you want to use, etc.

   1:  <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >

   2:   

   3:  <suite name="MyTests" verbose="-1" parallel="tests" thread-count="1">

   4:        

   5:        <parameter name="seleniumGridIp" value="localhost"/>

   6:        <parameter name="seleniumGridPort" value="4444"/>

   7:        <parameter name="testServer" value="http://myServer.domain.com:8080"/>

   8:        <parameter name="debugLevel" value="1"/>

   9:        <parameter name="dbEnvironment" value="dev"/>

  10:        <parameter name="testInfoSaveLocation" value="test-output/" />

  11:        

  12:        <test name="Edit Page Tests" preserve-order="true">

  13:             <parameter name="browser" value="*firefox"/>

  14:             <classes>

  15:                  <class name="com.packageName.BusinessListingPageTests"/>

  16:             </classes>          

  17:             <groups>

  18:                  <run>

  19:                      <include name="single" />

  20:                 </run>

  21:             </groups>        

  22:       </test> 

  23:  </suite>

The key to successfully running tests individually lies in lines 17 - 21.  By using groups, you can have your XML test suite run only those tests that you want to run.

The next step requires a few edits to your test classes themselves.  I'm using JAVA in these examples, but I'm sure that the principle relates to other languages as well.

For EVERYTHING you wish to have run along with your tests ( perhaps you have some database setup you want to do) , you must tell the Eclipse/TestNG unholy alliance that you want it to run.  This is simply accomplished by using TestNG annotations, as follows...

   1:  @BeforeClass( groups = {"single"} )

   2:  @Parameters({"browser", "seleniumGridIp", "seleniumGridPort", "testServer" })

   3:  public void setUp( String browser, String seleniumGridIp,

   4:       int seleniumGridPort, String testServer) throws Exception {

   5:   

   6:       Selenium sel = new DefaultSelenium( seleniumGridIp, seleniumGridPort,                                                                                                browser,     testServer);

   7:          

   8:       sel.start();

   9:       sel.open(testServer + LoginPage.PAGE_NAME);

  10:       sel.waitForPageToLoad("10000");

  11:  }

  12:   

  13:  @Test( dataProvider = "userSetup", groups = {"single"})

  14:  public void testChangeHoursOfOperation( String userName, String password,String businessId){

  15:       User user = new User();

  16:       user.userName = userName;

  17:       user.password = password;

  18:   

  19:       LoginPage login = new LoginPage(sel);

  20:       login.LISTING_ID = businessId;

  21:       login.setBrowserToStartPage();

  22:       login.loginUserName(user);

  23:   

  24:       assertTrue(amIOnTheStartPage());

  25:  }

  26:   

  27:  @AfterClass(groups = {"single"})

  28:  public void tearDown() throws Exception {

  29:       sel.stop();

  30:  }

That's it.  When you run the XML, now your single test will run all by it's lonesome.  When you don't want to run that single test anymore, simply remove the group from the @BeforeClass annotation.  It is very important, though, that you remember to include the group in the annotations for the setUp() and tearDown() methods, or they won't be run.  Its kinda hard to run a Selenium test if the IDE doesn't know where to find the Selenium Server.

I hope this helps someone.  If you have any questions, or feedback, please feel free to drop me an email and I'll be happy to clarify any point.

1. Don’t test a “Page.” Keep your classes and objects as small as possible.
   Do you allow someone to search for things on your website?  Then have a class/object that thoroughly tests your search.
   Do you have a coupon that shows up  based on the geo-location of a user’s IP address?  Write a class for that.
   Once you have your classes written for each the parts of a page you want to test, create a test file that instantiates those objects and tests them in the integrated format of the webpage.
2. Have your test do as little work as possible.
3. Keep the massive work in small functions that are publicly available for the object you are testing.

Do your work in a public method/function:

   1:      public boolean isPartnerLogoPresent() {

   2:          TestTools.debug(DEBUGLEVEL, "isPartnerLogoPresent()");

   3:          if (sel.isElementPresent(partnerLogoId)) {

   4:              TestTools.debug(DEBUGLEVEL, "\tFound the partner logo\n");

   5:              return true;

   6:          } else {

   7:              TestTools.debug(DEBUGLEVEL, "\tCould NOT find the partner logo\n");

   8:              return false;

   9:          }

  10:      }

Have your test call that function:

   1:      @Test

   2:      private void testPartnerLogoPresent() {

   3:          // verify that the Partner Logo is available

   4:          assertTrue(isPartnerLogoPresent());

   5:      }

On the surface, this might look as if you are doing a lot of extra typing and extra work, but if you have this partner logo show up on more than one page, all you have to do to verify it there is call this function.

While I acknowledge the fact that there is a problem with the nation become a 'fatter' nation over the last few decades, and that a more sedentary life-style added to an increased availability of cheap and unhealthy (when not moderated) foods plays a huge role in it's continuance, I am still adamant in my belief that it is not the governments purview to regulate any citizens life.
It may sound alarmist, only because it is a huge leap ahead on a pattern, but what happens when the government not only regulates what we can eat, but also the amount of exercise we are mandated to take in each day. After all, daily exercise is proven to improve one's health, and therefore lower the costs of health care for those who don't supply it for themselves. Do you happen to recall the opening scene of Orwell's 1984?
I'll oppose almost every little insinuation the government makes into my life to avoid being happy about my 10 ounce chocolate ration being increased to 8 ounces...

OK, those are the parts, let's get busy with an actual test.  We'll keep it simple and start with a single testcase.

*For the following instructions, things in RED should be steps that you take in FireFox. Items in BLUE are steps that you'll take in the Selenium IDE window.

1. Open Firefox to www.google.com
2. Open Selenium IDE by going to "tools" and clicking on "Selenium IDE"
3. Verify that your Base URL is set to "http://www.google.com"
4. In the search bar, type "Eddy Jones" and hit [ENTER]
5. Click the first link that will take you to estevenjones.com
6. Highlight the title "The Blog" on the estevenjones.com home page
7. Right click on the highlighted text and select "VerifyTextPresent The Blog" (this is one of the new Context Menu items that was added when you installed the Selenium IDE
8. Click "Hubble Space Telescope" link in the story about the Hubble Space Telescope (or any other link on any other story)
9. Right click on one of the images and hover over "Show All Available Commands >"   and from there, select "AssertElementPresent <some identifier here>"

In order to play back your tests, simply press the green arrow "play buttons" on the toolbar.

WHAT???  Why did my tests fail??

Well, your tests probably failed here, but that's ok.  This really demonstrates the speed of Selenium.  Your test most likely failed because Selenium tried to move on to the next step before the web page finished rendering.  So it tried to click on your next link before the link was actually on the page.  There are two ways to handle this.  The quick but bad way would be to adjust the speed of your test by adjusting the slider on the toolbar.  This would allow the web pages a chance to render prior to Selenium trying to act on it.  The better way to handle this would be to change the "click" commands to "ClickAndWait" commands, though.  This way, Selenium will wait for the page to completely render before moving on to the next command.  One thing to note about this method, however, if you are testing a page that has frames, you might run into problems with FireFox.  FireFox says the page is completed once the Frameset is complete rather than waiting for the contents of the frame have completely rendered.

Also before I sign off for this first tutorial, I'll mention the difference between Assert and Verify

When you ASSERT that an element is present, you are telling Selenium to stop the test and proceed no further if the assertion is not valid.  So, if I assert that an image is present and that image is NOT present, Selenium will not move on and all testing will stop.  The test will be marked a failure.

When you verify something is present, you are looking for something that is not terribly important enough to stop the entire test if it's not.

An example of when I might use assert versus using a verify:

If I loaded a web page displayed a render time, I might want to verify that the render time was under 5 seconds, but I wouldn't necessarily think that it's a total failure if it took 6 seconds to render.  I would want to use an assert to verify that it didn't take longer than 10 seconds because 10 seconds is way past my threshold for acceptable render times and there is no point in continuing my tests if it takes longer than that.

Stay tuned for the next session: "Creating Tests Suites"

Well, I'm here to bring your attention to this wonderful piece of technology.  Go take a look at some of its beautiful photos in the gallery.  I promise you, you'll be amazed at the stunning beauty that makes up our night time sky.

One mind blowing thing about this:  We are actually looking back in time whenever we look at stars and galaxies.  The closest star to us is 4.37 light years away from us.  That means, when we look at see that star system through a telescope, we are seeing the light that left the binary star system 4.37 years ago.  We are, in effect, looking 4.37 years into the past.  Now take that thought and apply it some of the most distant galaxies that the Hubble is able to peer at.  Billions of light years away...  We are literally looking at images of the universe from billions of years ago.  Creeping our perception ever closer to the beginning of it all.  That's about 700 million years since the Big Bang, or almost 95% of the way back to the beginning. Staggering to think about.  Read from the related articles below to learn more about this.

Related articles by Zemanta

1. A CLEAR AND CONCISE SUBJECT LINE / TITLE
   This might be the most important part of creating a good defect report.  With this, the people responsible for fixing the bug/defect and quickly group several similar or identical problems into one investigation.  A good description will have at least 2 elements:  An action taken and a result
   
   EXAMPLES:
   Bad:  The website isn't working.
   Good: Clicking on 'Home' link takes me to a "missing page" error page
   
   
2. CLEAR AND CONCISE STEPS TO REPRODUCE THE ISSUE
   More often than not, a majority of the time it takes to fix a defect or bug occurs in the "trying to reproduce it" phase.  Even if we track you down to have you give us a demo of the problem and that demo only takes 2 minutes, the time it takes to actually catch up with you and get that 2 minute demo stacks up quickly.  So, in the body of your defect, you should give developers more information than you think they could ever use.
   
   EXAMPLES: (We'll continue with the bug started in step 1)
   Bad:  I clicked home and was taken to a blank page.
   Good:
   1. I opened up a browser and navigated to our live site ( http://www.ourdomain.com )
   2. I logged into the site using the "Login" link
   3. I clicked on the "Message Boards" Link
   4. From Message Boards, I opened up the article "Summertime fun spots"
   5. I clicked on the "Add Comment" button
   6. I typed in a comment, but didn't hit [submit]
   7. I clicked on the "Home" button in the menu bar of the site
   8. I saw a blank page that stated the page was not found
   9. In the address bar, there was this URL:  http://joedeveolper.dev.ourdomain.com/home.html
   10. I'm using Firefox for my browser on Windows 7.
3. A RECORD OF REPRODUCTIONS
   There is an old and sometimes joked about adage that states "It's not a problem if was can't reproduce it." While this may seem rather flippant and careless, there's also a huge grain of truth in it.  Sure there may have be an actual problem, but in the terms of prioritization, I'm sure it's easy to see that a defect that is either un-reproducible or difficult to reproduce is less important to fix than something that happens all the time.  Of course, this is an over-simplification as a bug that wipes out all of your data, even if it is almost impossible to reproduce is pretty damn important.
   
   EXAMPLES:
   Bad: I think I heard someone else had this problem
   Good: I was able to reproduce this on Internet Explorer, too.
   Best: I was able to reproduce this on Internet Explorer too.  I also got Sally and Jim to reproduce it on their computers, as well
   
4. SCREENSHOTS OF THE PROBLEM
   If the problem is visual in nature, it's always a good thing to include a screen capture of the problem.
   
   EXAMPLE:
   "The background color for the Name and Description columns do not match on the albums listing page."
   
   
5. ADVANCED TECHNIQUES: Recording a macro to reproduce the problem automatically
   There are many tools out there that will allow you to record all the clicks and typing you do on your computer.  Recording these actions could prove to be very helpful to the people trying to fix your defect.  Even if you list all of your steps as accurately as you believe is possible, there might be something that you do, thinking it's insignificant, that the developer will catch on and realize exactly what the problem is.  Perhaps you clicked on the graphic of a button rather than its, text.  Perhaps you submitted a form by hitting the [Enter] key on your computer rather than clicking the [submit] button on the web page.  Another major benefit of recording your actions is that your recorded actions are now documented, and it might be possible to create an automated test from them.  With an automated test, your defect might be caught next time before it ever gets to a production environment.  Keep in mind, these tools record your actions ( move mouse here, click here, type this ).  It does not record a video of what you see.
   
   SUGGESTED SOFTWARE:
   
   Bad Boy a very nicely done tool that is, unfortunately, a windows and Internet Explorer only tool.
   
   Selenium IDE:  This tool is also a very good program.  It sits on your system as a Firefox Plugin.  So initial recording of a defect will be done in Firefox only, but it can be played back using several different browsers.
   

These techniques and suggestions are not the be all and end all of 'best practices' for reporting a bug or defect, but they will certainly get you further down the road in being a productive partner when it comes to making sure your company produces the highest quality software.

The glumblefilch sauntered into the room.  He was full of vim, vigor, and veracity.  His three blandlybulches protruded from his torso, nearly touching the floor and he admired them.  They were long and elegant.  Fragile looking but he knew they were sturdy.  The purplish hue they emanated set off the radiance of his six yellow eyes.  Most glumblefilches only had five eyes, but he had six.  He was quite proud of that, even if the other glumblefilches looked at him askance for his audacity, he had just one more eye that he could roll at their ignorance.

This glumblefilch was named Snodgrass.  That was not something he was particularly proud of, but it was his name.  He bore it with resolution and aplomb. He honestly didn't care what the other glumblefilches said about it.  It was better than Steve, Victor, and Roger. And it was miles above Roderick.  Roderick only had 3 eyes, Snodgrass mused, shaking slightly in his mirth.  A low chuckle escaped his lips.  Normally that would be fine, but tonight Snodgrass was with his boy at dinner, and a glumblefilch's low chuckle was actually quite a rumble.  His boy gave him a warning glance over his shoulder and Snodgrass settled down.  He didn't want to get his boy in trouble again. Last time that happened, Snodgrass wasn't allowed to come out from under the bed for a whole week.  That was torture.  Glumblefilches aren't known for there ability to handle solitude.  They need constant attention and reassurances or else they disappear.  By the time the week was over and his boy again came looking for him, Snodgrass had faded to near invisibility.  A couple hours later though, fueled by the laughter of his boy and the games they played together, Snodgrass was back to his three limbed, six eyed purpley self. 

The boy's mother had stuck her head into the room looking about curiously. "Who were you talking to?" she asked, her half smile showing she wanted to share in the fun.

"Just Snodgrass,"  the boy had answered.  With a confused look, the mother left the room.

So ... not wanting a repeat of a week under the bed, Snodgrass promised to be good during dinner.  He floated down to the floor folding his blandlybulches beneath him. 

He tried.  He really did.  He wanted to sit and wait quietly, but he was just not good at that.  After a few moments, he couldn't take it anymore.  He had to do something.  So, Snodgrass pulled himself into the tightest ball he could and rolled under the boy's chair.  Giggling softly to himself (this was going to be hilarious), the glumblefilch gulped and swallowed three big mouthfuls of air. Then he waited..   He could feel the air wanting to escape.  He held it in... He held it in more..  He giggled... Then he couldn't hold it anymore.

Remember when we talked about the rumbling of a glumblefilch's low chuckle?  Well, imagine what a full fledged belch would be like.  The silverware on the table rattled.  A Glass fell over, spilling milk onto the table.  The curtains flapped in the breeze.  The boy's mother fell over in a dead feint (OK, well almost).  The boy's father had the look of horrified disgust.  The dog ran into the living room, looking for a reprieve.  Low flying aircraft swerved crazily, looking for where that clap of thunder came from.

When the echoes died away, when the mouths of both parents closed, trying to hide their disbelief and the glumblefilch under the boy's chair fairly split in two trying to contain his mirth, the boy glared under his chair.

"SAMUEL!!!" the boy's mother admonished.

The boy looked astonished, "It wasn't me, Mom!!  It was Snodgrass!"

Samuel's father looked at him angrily.  "Young man, that is not the way we behave at the table.  And I've told you before.  There is no Snodgrass.  There is no such thing as a glumblefilch!!"

Snodgrass hmmphed quietly to himself. "No such thing??" he thought, "What does he know?"  In a rage, he rolled out from under the chair, hovered up to the height of the table and stretched out his blandlyfilches to their full reach. 

That's when he noticed he wasn't there.

For a moment, I lost sight of my prize.  I saw only the rocks and grass at my feet.  Struggling to catch my breath I stood up straight again and smiled as my vision locked again just over the shoulder of this behemoth that was pummeling me.  This time the punch to the face hurt.  I'm pretty sure I heard the loud crunch of my nose breaking as his fist connected.  I know I tasted blood. 

This blow actually knocked me off of my feet.  I sprawled backward into the bushes that lined the side of the house.  Groaning with the fire that seemed to be consuming my face.  WOW!!! That hurt like hell!!  The behemoth was yelling something at me now, but I couldn't make out what he was saying.  Having rebounded off of the bushes, I was lying on my stomach inches from his feet.  Lord, please don't let him be pissed off enough that he's going to kick me...

As the ringing in my head began to taper off, I'm was able to make out what he was shouting, "Get up you little bastard!!" or something to that effect.  He moved to the side of me and kicked me hard in the upper thigh. "Get up!!"

With a Herculean effort, I pushed myself up, unsteadily rising to my feet.  I glanced back at what had been holding my rapt attention in disappointment.  The moment was gone, time to retreat.  I tried to find my way around this bruiser,  tried to find my way to the street so I could get home and nurse my broken face.  He shoved me, roughly.  I hit the side of the house with a sickening thud. My head slammed against the paneling with a sickening crack.  I prayed that it was the wood and not my skull that split.  The sasquatch grabbed the front of my shirt, holding me upright so he could deliver another punch to my face.  "I'll show you!!" he bellowed, "You fuckin' pervert!!"

We were both startled by a scream from above us.  "STOP IT!!!"  The shrill voice came from directly over our heads, from the bathroom window.  Cyndi was leaning out of it, her face filled with horror and a bit of fear.  "What the hell is wrong with you??"  The light behind her shimmered on her wet golden hair, creating a nimbus of light around her. Her robe was pulled tightly around her now, I guess she'd finished drying after her shower before sticking her head out the window to see what the commotion was about.  Despite my blood spattered face and probably already swollen nose, despite the pain in my gut, and the pounding in my head, I managed a weak smile. 

Jared, her older brother still held me, his fist ready for that final blow. "This little perv was watching you!!"  he yelled, much too loudly for my throbbing head.

She looked down at me then, perhaps a slight flicker of recognition in her eyes.  I could see that she was torn, emotionally.  Angry at having been spied on.  Embarrassed she had just stepped out of the shower, and I'd probably seen her drying off and putting on her lotion before the pummeling began.  Concerned, because I'm sure I looked a mess.  Hopefully I didn't look as bad as I felt.  After an appraising second, she said, "Let him go Jared, he's just a kid."

"But.." Jared began, obviously wanting to pummel me a bit more.

"Let him go, you've beat him up enough.  He'll never do it again."  With a pointed look at me she asked, "Will you?"

I was a bit miffed at being called "just a kid." She was only a few years older than me after all.  She's a senior though, and I guess we're all kids to her.  I shook my head in a silent promise that I'll never peep on her again.

"Let him go," she repeated with finality.

With reluctant glare, Jared gave me a hard shove in the direction of the street. "If I ever see you around here again, you'll get worse!" he promised.

I made my way toward the street, toward home.  Jared was making his way back into the house through the side door and was quickly out of sight.  Cyndi was still leaning out the window, watching me leave, a curious expression on her face.  If you asked me today, I would still swear there was a slight smile on those lips as I walked away.

So was it worth it?

Yeah..  It was worth it...

-E Steven Jones

She saunters to the table, wearing that little black dress that she knows I love to see on her.  Her smile tells me that the drink in her hand isn't her first.  It's comfortable, relaxed, happy, and not just a little flirtatious.  The music in the background is soft, but evident and her hips sway unconsciously to it's rhythm.

"Are you just going to sit there all night? Or are you going to get up and join the rest of us?" She asks me.  I wonder if she has any idea of the effect that she has on me?  I almost groan aloud, but catch myself in time as I watch her put the straw from her drink to her lips.

I manage to keep my voice friendly and nonchalant. "Oh, I dunno. I'm having plenty of fun watching all you drunks making fools of yourself out there dancing," I joke.

"Drunk?!?!" she asks, her smile tells me I must have just unknowingly challenged her. "You haven't seen anything yet." My heart aches as she reaches for my arm to drag me away from the safety of the table.  A jolt of electricity jumps through me as her skin contacts mine. "C'mon," she tells me, dragging me to my feet, "You've been the playing the recluse long enough."

I'm hoping that she doesn't notice the melancholy smile on my face as I reluctantly rise.  I can't help but stare at the little gold ring around her finger, wishing I was the one who put it there.

For the rest of the night I have to watch her dancing with the rest of our group.  We're all out here tonight after finally closing the deal with our biggest client to date.  Too many hours we'd all spent at our tables, making little changes requested to the facade, the landscaping, the lighting of the office building for a 'to be named later' law firm.  But the deal was done, and now we're all out at this "intimate" little jazz club she'd gone to a while back.  I know that I'll be having the same dream tonight that I've had almost every night since all these late work nights started.

It's a simple dream, really.  I'm walking down the street with her on my arm.  Sometimes it's just the two of us, sometimes we're with a group of friends.  Sometimes I'm quiet when I tell her, sometimes I'm shouting it out to the world.  But the words are always the same.  And as I watch her on the dance floor now, they still are the same and I want to tell her, "I love you."

I stagger into work the next day, having slept very little.  And of course she's there.  With a ready smile and a cheerful "Good morning." My heart flutters at what I think is a one of those "meaningful stares" that I hear so much about.  But I fall back again from my reverie, almost immediately.  She reaches up her hand to brush a gorgeous strand of hair that has fallen over her eyes.  Her left hand.  The hand with that blasted little gold ring.

I resign myself to the rest of the day I have ahead of me. I try to bury the thoughts rushing through my mind, the electricity coursing through my body.  I know that she'll never be mine and that all of my "I love yous" are going to have to remain my secret, and all of my dreams and desires are going to have to remain my hidden midnight confessions.