Ciaos Creations

During the past few months, both Amazon and Paypal has announced mobile payment systems on their respective platforms. Listening to reports on mobile payment usage in India, Africa and Japan has me wondering if or when the United States will ever adopt the behavior.

Yesterday I read Caleb Elston’s post on mobile payments titled “Are Mobile Payments the Next Big Thing?“; it was very good read. The payment process he described was a process that I believe is simpler than I thought was possible. Before, my assumption was mobile payment would be possible through a mobile web app or a native mobile app.

There were other thoughts going through my head besides implementation, such as what are the use-cases mobile payments would be preferred over the traditional payment methods, e.g. cash and credit.  Mobile Payment Adoption will be a challenge due to the habits and existing infrastructure for cash and credit.  So lets just jump around to a few examples.

Digital Goods, Online Shopping
When buying digital goods or shopping online, mobile payments work well in this type of scenario mainly because the check-out process is asynchronous between the buyer and seller, which the seller is an automated machine.  The maximum number of simultaneous check-outs is almost infinite for these shopping experiences, mainly limited by broadband and server resources.  This example could be consider as a natural progression of commerce from a desktop device to a mobile device.

Simple Singular Transaction
This tangent is sprouted from how Japan and some privileged American Cities purchase their train tickets.  Purchasing train tickets scenario is a simple process of fee that rarely change. Mobile Payment could be automated in that it is just a quick swipe of the mobile device or gateway  that initiates the transaction.  This example is rather simple and somewhat uninteresting. It is a substitution of the payment medium.

Physical Stores or Merchants
All of us are familiar with the process of making purchases in the physical space.  Walking from aisle to aisle, acquiring physical goods, to check-out by standing in a queue to a limit number of cashiers.  This example is synchronous, both the buyer and seller have to interact in real-time, both of which are human.  This is the scenario in which I am interested to see how mobile payment has an affect.  I find it to be my largest pain point and an experience that could be improved on. Changing the habit of purchasing physical goods is and will be a very difficult task.

So those are the first three use-cases that are floating in my head. I intend on promoting mobile payments, but I am just having trouble finding a good scenario that mobile payments can improve upon.

That is it for now.

@plightbo

The Setup / TearDown instructions found at http://seleniumhq.org/projects/core/usage.html explains a work around to the issue, however the work around is not the technique I expected.  I am personally most familiar with setup/teardown methods that executes before and after each test case.

Just to throw it out there, a function call that opens a given link page, then executes selenium commands found there, which then after completion would return to the original page would probably be what I would be expecting.  

The workflow behind the Test Suite would probably has a function that I am searching for.  It is similar in that the flow of control starts by opening a test case, executes the commands, then returns to open another test case if available.

Here is a quick crude example in pseudocode of what I am imagining.

File: login_user.html
Login User

•  open(“/home”);
• type(“usernameField”, “apple”);
• type(“passwordField”, “password”);
• click(“submitButton”, true);
• assertLocation(“/dashboard”);
   

File: logout_user.html
Logout User

• click(“Logout”, true);
• assertLocation(“/home”);
   

File: test_invite_friends.html
Test Invite Friends

• execute(“login_user.html”);
• click(“create event”, true);
• verifyText(“Invite Friends”, true);
• execute(“logout_user.html”); 
   

Ideally, I would like to declare the Setup/Teardown functions in the Test Suite page instead at the beginning and end of each unit test.  However I noticed that the Test Suite is only single column table;  I am unsure how difficult it would be get Selenium to support multiple columns. 

Here is an example of a test suite file in HTML.

<html>
<head>
<title>My Application Test Suite</title>
</head>
<body>

<table>
<tr><td><b>Suite Of Tests</b></td></tr>
<tr><td>Setup</td><td><a href=“./setup.html”>Test Login</a></td></tr>
<tr><td>Teardown</td><td><a href=“./teardown.html”>Test Login</a></td></tr>
<tr><td><a href=“./TestLogin.html”>Test Login</a></td></tr>

<tr><td><a href=“./TestFormEntry.html”>Test Form Entry</a></td></tr>
<tr><td><a href=“./TestFormSave.html”>Test Form Save</a></td></tr>
</table>

</body>
</html>

Please let me know if I need to provide more details or a better written explaination.
- Thanks

@whereisciao