Apple raised some eyebrows over the weekend when news unfold it had hired an knowledgeable in mobile payments.

However now there’s a report that says the company is already testing a prototype iPhone with near-subject communication (NFC) chips inside, which may pave the way in which for utilizing future iPhones as a cell wallet.

TechCrunch heard from an unnamed source that on Tuesday Apple is testing an iPhone with NFC chips it’s ordered from NXP Semiconductor. It is not clear what kind of assessments, and it may very well be very preliminary in nature. However coupled with the hire of Benjamin Vigier from mFoundry as cell payments product manager, it does appear possible that Apple might be planning to open up its premier product to the world of commerce outside of iTunes.

First, what’s NFC? It’s a know-how that enables knowledge to be sent wirelessly over very quick distances, around 4 inches. It sends information from a chip inside a device like a cellphone, to a fee terminal, and even one other device. Whereas cell payments is an obvious use–that is used in places outside the U.S. for things like paying bus or practice fare–it’s not the one one. It is also used to transfer knowledge between units very near one another, say an iPhone and a laptop.

Among the most extremely trafficked interactive techniques in the present day are accessed via the Net: Amazon.com, Facebook, Google, Zynga simply to call a few. These apps need to work flawlessly throughout any browser or danger dropping eyeballs and audience consistency.

The browser wars in spite of everything, are still alive and properly, and any critical Web utility must work on the most popular browsers , comparable to Internet Explorer, Firefox, and Chrome but do not forget others like Safari and Opera.

However for many companies, it is troublesome and costly to take care of and update a check infrastructure on premise that retains up with the top browsers and all their releases, major and maintenance. Like growth and deployment before it, the time has come for cross-browser testing to maneuver to the cloud.

Earlier this year, start-up Sauce Labs launched Sauce OnDemand, a cloud service that allows users to execute their Selenium scripts in parallel across 10 of immediately’s hottest browsers. In accordance with Jason Huggins, the creator of Selenium and co-founding father of Sauce Labs, browser testing is a see-it-to-consider-it type of thing. Builders are used to seeing exams working locally however usually lose that visibility when testing moves to the cloud.

Sauce Labs on Thursday is anticipated to introduce Sauce TV

Steve Feloney is the face of HP’s Performance Centre. I met Stephen a year ago as he was doing a world tour to endorse Performance Centre. Stephen is passionate about Performance Centre. He does his work well, and you can’t avoid agreeing with him about Performance Centre and its value.

Now Stephen has written an article about PC and how you can get a great Return of Investment (ROI) even though PC is itself very dear to buy.

It goes something like this……If you were to travel from London to Rome, a car would be a very nice idea. To get a car, it will price you a lot of cash to buy one, but it is much easier than doing the journey by foot. It would take two months to walk, and as a extremely well paid IT worker, the overall cost of the voyage in terms of lost income would without difficulty cover the price of a car.

To my mind, there are other forms of transport like public transport. It is a much less expensive option, however, the voyage is longer and a lot less comfortable. That is the same with PC, you don’t necessarily have to obtain the best possible option, you can look downmarket and that will pretty much facilitate you to achieve the same ends.

You can make up your own mind.

The trouble with using a data centre is the service provider does not always respond to queries. I was in recent times asked by a client look at an issue concerning a hosted website.

The problem was a website which was running slow. I wanted to know what they had changed recently thinking that something they had done may have caused a problem. They told me that they hadn’t made any alterations of late, it had simply started to perform poorly suddenly. They did state that some time back they had made performance improvements on their website by by installing compression and by making any images on the site more efficient. They had checked the performance after these changes and the website was running well and had been for quite some time now. The reduced performance had started a couple of days earlier and they were certain the performance problem was due to the data centre where the website was hosted.

A study was started to see what was occurring. The opening thing I did was to execute a ping. This can be initiated from the command window (from the start windows prompt, type ‘cmd’ and enter. The command itself is simply “ping www.testingperformance.org” This generates 4 requests to the website each with a packet size of just 32 bytes. It’s pretty small, and the response should give you a good idea of latency. Of the 4 hits, twice out of 4 the replys timed and the remaining 2 took over half a second. That is not very quick. There are a variety of options with ping. “Ping -l 200 www.testingperformance.org” will ping the website with 200 bytes. While this is still very slow, it can be increased quite simply to 100Kb which is more realistic of a big web page.

As I was in Britain and the website was located in the North America, I wondered if the latency could be owing to the distance across the Atlantic. To answer that query, I ran a trace route. The format of the command is “tracert www.testingperformance.org” This should demonstrate the various hops that are made when accessing from a workstation or laptop to a server or website. What I could see was that the last 2 or 3 jumps (out of about 20 jumps) were extremely sluggish. It was possible that these hops were in the data centre itself.

I conveyed this information to the data centre and said, look, here is substantiation, are these hops with reduced reply times caused by your equipment? The data centre people in due course contacted me back and stated, they could not tell a lie, the answer was no, it was not them. Well I knew it wasn’t me, and I knew it was not my ISP, and the data centre said it wasn’t them, but I didn’t believe them.

Scouring the net, I located some tools I considered should help, one was named IWEB. I downloaded the tool and it checked the homepage on my website for an interval of time. The results showed response times varying between 2 seconds and 25 seconds. I sent this data back to the hosting centre and asked them to make a statement.

“Oh yeah,” they said, “oh there has been a issue with {one of the} sites on our hardware, it has been receiving lots of hits recently.” “hang on a second,” they said. Half an hour later, my clients site was delivering 1 – 2 second response times again. The assumption was we had been moved to a better performing server. Well, I guess we were ok, but there remains around 90 – 100 websites still hosted on the hardware with performance issues? It wasn’t that we complained, it was showing the evidence which managed to settle the issue for us, thanks to IWEB.

Application code testing is time consuming and needs outlay in funds and time and frequently results in documentation, procedures, test data, test environments as well as a working software. There is an attraction to skimp on testing as it is an costly business. Application code testing is indispensable.

If the application is unusable when it goes into production, it will cost much more to fix those issues then than it would have if testing had been undertaken before implementation. Fixing defects in live is an expensive matter, it makes pre-production testing look cheap.

How much testing must be done? There is no right or wrong answer to this. The longer that testing carries on, the better the implementation might be. The cost of finding defects increases as testing continues.

While perfection with testing is theoretically possible, it is seldom achieved, the expenditure is simply too great.

Testing assets are not usually thought of as an asset. Financially, testers are seen as a negative not a positive on the balance sheet. Test environments are expensive and are not seen as obligatory and valuable. A server has a definite base cost, a server installed with an application to be tested complete with test data may cost 10X. With many test scripts the testware is worth a good deal more than the hardware asset itself that is listed on the balance sheet.

While this does seem like a cost, it’s not, it’s an asset. The test pack can sustain the implementation of future business requirements going forward.

Generally, much effort is spent executing testing cycles. Now with the introduction of automation and when used in tandem with a test management tool, much of the testing exertion is spent installing code drops, tracking faults and fixing them. There is a financial bottom line value to testcases and the ability to execute them. Good well written testcases supported by a good test management tool and a well configured supported test environment are valuable.

Test automation can increase the worth of the testpack. The setup costs for test automation are high, but the benefits to the testing process are also high. One of the key benefits is that the time to test is greatly reduced. While automated testing itself is much quicker, sometimes just taking a few hours, it can also be run overnight. If the code was ready for testing late on a Tuesday, the test execution could be completed by first thing on the Wednesday.
Generation of an automated test pack is a specialised task using software licenses that can run into the thousands for a single license.The planning stage is considerable with much thought going into determining the keying steps. Test automation uses a substantial amount of logic so that it can adapt to diverse situations when executing against the system frontend.
A test automation specialist will ideally make sure that test automation code does not need to be updated every time the application under test is changed, although sometimes, changes are required if new objects are added to the software screens.

Certainly test automation built with little thought can become a genuine expense to a company, not an asset.

Effective test automation resolves each of these issues, allowing management to:

* A reduction in quality assurance resource – thereby making testing cheaper
* Quicker testing and bug resolution cycles
* Better visibility of test results

What can be done to make the automated quality assurance process more effective?

The method is driven by an effective methodology. Without an effective the automated testing practice can quickly turn into an expensive waste of time. Methodology is critical. The entire process should be driven by Methodology- from tool selection to the way in which the tool is applied.. It also helps to drive the approach to off shoring the “appropriate” pieces of the quality assurance process.

The following offers a check list for a Test Manager to follow when applying an automated quality assurance methodology

10 Essentials for Effective Test Automation:

1. Know the steps of the software development process and how they relate to each other.
2. Clearly document the corporation requirements, hardware requirements and software requirements that are necessary to support your automated quality assurance process.
3. Understand that Quality assurance is a strategic effort.
4. Commit to giving software testing its own budget and funding.
5. Choose the right enabling technologies to support the quality assurance process.
6. Be very careful to ensure that the people used to build the automated testing framework are experienced and or trained.
7. Separate test design from test automation so that automation does not dominate test design.
8. Be very careful when considering to lower costs by using less expensive labor than a local team.
9. Document the goals within a test strategy and best practices for test design in a test plan.
10. Use a company or a person with the appropriate skills to build the baseline foundations of your automated testing framework