API Automation platforms

API automation platforms:

	Cloudwork - Cloudwork is a service that allows users to automate tasks between Google Apps, Salesforce, Evernote, Zoho, Twitter, Freshbooks, MailChimp, Zendesk, Dropbox, WordPress and others.
	Elastic.io - Elastic.io is an API integration and orchestration platform for non programmers, offering a simple tool for users to create and run data/API mashups directly from the browser, to automating simple tasks between API platforms.
	FoxWeave - FoxWeave enables enterprises that are building or using Cloud based Services (SaaS, DBaaS etc) to connect those Services to each other and to external Cloud and On-Premise Apps and Databases.
	If This Then That (IFTTT) - IFTT is a service that allows anyone to built connections driven from APIs by building channels made up of triggers and actions, bundled into whats IFTT calls recipes, which are triggered every 15 minutes.
	MashableLogic - MashableLogic is a mashup development platform that provides a system for leveraging API's by turning them into re-usable components that can be combined to compose software solutions.
	Tarpipe - Tarpipe provides a platform for automate tasks, creating workflows between apps to automate low value tasks, generate activity streams from multiple apps in one place, sync data from one app to another as a background task, and publishing of content to multiple API locations.
	Wappwolf - Wappwolf is focused on deconstructing the barriers of the Cloud, by connecting your Evernote, Facebook, Flickr, and other web services / apps to Dropbox, allowing users to drag & drop files into a predefined folder on Dropbox and automatically convert and sync to your favorite places.
	We-Wired Web - We-Wired Web enables users to define automated tasks using over 50 popular web services using APIs that execute periodically.
	Yahoo Pipes - Pipes is a composition tool to aggregate, manipulate, and mashup content from around the web. Like Unix pipes, simple commands can be combined together to create output that meets your needs.
	Zapier - Zapier uses what they call a zap to deliver a combination of a trigger and an action using APIs, allowing users to drag and drop to build new zaps and run in background or manually from a dashboard.               JBlack a java api test automation tool - http://jblack.sourceforge.net/

Selenium IDE - How get Current - date, month, year & time through script

Selenium IDE - How get Current - date, month, year & time through script


There are many ways like as below:

1.

Current Time - javascript{(new Date().getHours()+" : " + new Date().getMinutes() + " : " + new Date().getSeconds())}

Current year - javascript{(new Date()).getFullYear()}

Current Month - javascript{(new Date().getMonth()) + 1}

Current date - javascript{(new Date().getDate().toString())}


2. 

<tr> 
        <td>storeEval</td> 
        <td>var d=new Date(); d.getDate()+'-'+((d.getMonth()+1)) 
+'-'+d.getFullYear();</td> 
        <td>date2</td> 
</tr> 
<tr> 
        <td>echo</td> 
        <td>${date2}</td> 
        <td></td> 
</tr> 

3. 

Selenium Auto IT

Selenium Auto IT

http://bhimarajumavuri.blogspot.com/2010/02/selenium-autoit.html

More about Prototyping methodology ....

Prototyping Model

The prototyping model assumes that you do not have clear requirements at the beginning of the project. Often, customers have a vague idea of the requirements in the form of objectives that they want the system to address. With the prototyping model, you build a simplified version of the system and seek feedback from the parties who have a stake in the project. The next iteration incorporates the feedback and improves on the requirements specification. The prototypes that are built during the iterations can be any of the following:

• A simple user interface without any actual data processing logic
• A few subsystems with functionality that is partially or completely implemented
• Existing components that demonstrate the functionality that will be incorporated into the system

The prototyping model consists of the following steps.

1. Capture requirements. This step involves collecting the requirements over a period of time as they become available.
2. Design the system. After capturing the requirements, a new design is made or an existing one is modified to address the new requirements.
3. Create or modify the prototype. A prototype is created or an existing prototype is modified based on the design from the previous step.
4. Assess based on feedback. The prototype is sent to the stakeholders for review. Based on their feedback, an impact analysis is conducted for the requirements, the design, and the prototype. The role of testing at this step is to ensure that customer feedback is incorporated in the next version of the prototype.
5. Refine the prototype. The prototype is refined based on the impact analysis conducted in the previous step.
6. Implement the system. After the requirements are understood, the system is rewritten either from scratch or by reusing the prototypes. The testing effort consists of the following:
   • Ensuring that the system meets the refined requirements
   • Code review
   • Unit testing
   • System testing

The main advantage of the prototyping model is that it allows you to start with requirements that are not clearly defined.
The main disadvantage of the prototyping model is that it can lead to poorly designed systems. The prototypes are usually built without regard to how they might be used later, so attempts to reuse them may result in inefficient systems. This model emphasizes refining the requirements based on customer feedback, rather than ensuring a better product through quick change based on test feedback.