IBM Rational community
Tim_Hague 060000WUM5 Marcações:  open_source qa flash rft framework adobe flex automation 5.742 Visualizações
Today I published an article to developerWorks that describes how our team was able to extend RFT to allow us to more consistently recognize the GUI objects in a Flex/Flash application. As you probably know RFT does come out of the box with Flex application automation support but it does not keep up with the constant browser and Flash plug-in updates. Even if you are not specifically testing Flex applications the article will help you see a hands-on example of how RFT can be extended, after all we tend to forget that RFT is a full fledged Eclipse IDE that can be molded into whatever kind of tool you need to solve various automation problems.See the article linked below:
How do you extend RFT?? I'd love to hear!!!
Patty_Orben 2700024708 Marcações:  rational_change rational_functional_teste... rational-method-composer rational tomcat automation automate 4.704 Visualizações
Automating whenever possible standardizes processes and frees developers' time for other projects. In separate articles, authors Ricardo Balduino and Richa Awasthy share with you how to automate for success. In our third article Pradeep Shashidhar teaches you how to deploy Rational Change on a Tomcat server.
By Ricardo Balduino, Senior Software Engineer, IBM, USA
Ricardo Balduino describes how to take a process already defined in Rational Method Composer and automate it in Rational Team Concert. This makes it far easier and faster to adopt proven patterns of success and also makes it possible to ensure that people follow them.
Products: Rational Method Composer, Rational Team Concert
By Richa Awasthy, Staff Software Engineer, IBM, Australia
Richa Awasthy gives an overview of Rational Functional Tester Version 8.2.1 support for Flex 4.0 and 4.1 SDKs. Then she explains how to automate testing of Flex Spark applications.
Product: Rational Functional Tester
By Pradeep K. Shashidhar, Advisory Software Engineer, IBM, India
IBM Rational Change 5.2 includes the Jetty 5.1.14 web server, and you can also deploy it with IBM WebSphere Application Server or WebSphere Application Server Community Edition. However, there is no option in the installer to deploy Rational Change on a Tomcat server. This article explains how to do that.
Product: Rational Change
This week we are also highlighting the following items on our home page and product pages that you may find of interest.
JoshGalde 270005VQUH Marcações:  level device automation mobile systems rational deviceanywhere testing object keynote test ibm 4.973 Visualizações
For Desktop-based testing it’s a no-brainer: Use object-based scripting to maximize reuse across platforms/browsers. In today’s mobile world it really isn’t that simple. There are many different platforms, OS versions, form factors and carrier/manufacturer customizations. Multiply that by mobile web, native app, or some hybrid in-between and you’ve got yourself a healthy testing matrix. A daunting task for even the most skilled Automation Engineer.
In order to tackle this problem, an Automation Engineer cannot simply look at it from a “one size fits all” perspective to create a set of objects and re-use them across all combinations of platforms. For example, there are fundamental differences in how an app behaves on iOS and Android, even with something as basic as a “back button” has its quirks.
Although these fundamental differences can be grouped together as a step or action, they are unique enough to not be able to simply share an object between the two OS’s.In some cases with mobile testing, you may be able to get to the object-level, however this usually requires that you instrument your app, or test on an emulator. While this fulfills a piece of your testing matrix, you will probably need to seek a couple tools to get this done across all platforms. In other cases, the content you are testing might be HTML-based and you can test by WebKit profiling. Again, part of your testing matrix is fulfilled, however you aren’t quite there.This may be enough to satisfy a short-term goal, but at some point you need to be testing on real mobile devices.
In order to truly automate on mobile, your mobile testing “Utility Belt” needs to be designed in such a way that allows for testing by object when possible, element when possible, and also be able to quickly fall back on text or image verification in order to satisfy all areas of your testing matrix and assure the highest quality of your mobile product. Having the flexibility to be able to choose how to get the testing done is paramount since as an Automation Engineer,you very rarely have a say in how a particular app or mobile web site is developed. The job requires you to sometimes understand functionality without necessarily being privy to the construction, and there is always a tight timeline to achieve results. The right tool for the job is a tool that takes all of this into consideration, and provides a platform to consolidate all of these different types of testing approaches.The first step is to determine the type of app you are testing. Is it fully native, fully web, or somewhere in between?
The second step is to find which pieces or steps of your test cases are reusable between each other, and can accept parameterization to fulfill the task. For instance, automating the selection of an item or link on your main screen of your app or landing page: Maximize reuse by engineering a parameter to accept different values, and reuse it across each test case. Although you may need to individually determine what type of verification you will use to achieve this on a per platform or device level, you will save time in the long run when you write additional test cases. The third step is to then group those pieces or steps together by device screens or pages. This way, as you write the test cases you have an organizational structure that is easy to identify by where you are within the app or site and where you need to navigate to next.Following these steps will provide a structure that can be grown to accommodate new features within an app or new sections within a mobile web site. As mobile devices become easier to automate against, this structure can easily adapt to emerging technologies that allow for greater reuse across platforms.
Note: This article was recently published in the April, 2013 issue of Automate Software Quality Magazine.
JoshGalde 270005VQUH Marcações:  developer systems applications keynote device application app firefox smartphone android ctia mozilla object test smartphones level windows apps iphone automation os fragmentation developers qa blackberry enterprise testing scripting ios google store native html5 mobile mobility object-level web deviceanywhere 6.740 Visualizações
Depending on your application, you will have to assess whether testing on an emulated device or real device is the best option. Many times it is not either/or decision and the best choice is both. Emulators offer the less expensive testing option, but they have many limitations for mobile testing and may not give an accurate depiction of the mobile user experience.
However, as part of the mobile testing process the use of emulation has an important role. There is certain testing that you can conduct with emulators that are sufficient which include testing for screen size or visual form factor. However, emulation is often an approximation of the rendering and can only get you so far.
Leveraging emulators is a positive step towards real device testing, however, not sufficient for comprehensive testing needs. With cloud-based testing you no longer need to have a bunch of people in a room with different mobile devices.
Testing on real devices gives the tester full functionality of the mobile device. While device types may be more limited than the emulated devices, testers should be able to have access to the real processor and hardware to understand the quirks that some real device have. Without this ability, users may not discover some real life issues that device differences would present in a real environment versus in an emulated environment.
It is important to conduct real device testing when needing to test mobile engagement with the device, launch applications, and interact with device at a more detailed level.
Keynote offers some useful free tools to perform mobile testing. Developers and testers can quickly conduct interactive functional testing on their websites from the convenience of their desktops with remotely accessed real devices and an accurate device emulator. To read more click here!
JoshGalde 270005VQUH Marcações:  deviceanywhere os html5 automation firefox native mozilla testing object windows ios test qa device developers mobility mobile fragmentation app developer object-level iphone scripting smartphone systems apps android store keynote web application smartphones google enterprise blackberry level applications ctia 6.194 Visualizações
Automating your mobile testing has two main advantages, increasing efficiency and cost savings. With automated testing, imagine you are able to conduct manual tests with simple scripts and run it repeatedly. You save human resources and money. Automated testing helps QA teams quickly create and test scripts to capture, verify and replay user interactions.
Every second saved by forgoing continuous manual input adds up, thus relieving the stress and resources, enabling testing to be streamlined. Some companies are able to automate all of their mobile testing. Depending on the type of app you are testing, at least 80 percent of it can be automated, however, factoring app functionality on different devices and platforms, there is often a need to supplement it with ad hoc manual testing.
Leveraging the tools that help measure and evaluate the quality of your mobile app or website, you can use real device testing or automated scripting to assess the quality of services. This will help you to determine the user’s experience in the environment of the App or service once its launched.
To read more about why you should automate go here.
JoshGalde 270005VQUH Marcações:  fragmentation developer deviceanywhere google keynote developers ctia level automation android enterprise mobile applications forrester blackberry store firefox test smartphones os device scripting windows smartphone gartner app idc application iphone web qa mozilla apps object testing ios object-level native html5 systems mobility 6.619 Visualizações
Over the last 5 years since 2007, we have seen an explosion in mobile apps to make our lives convenient and more efficient. And it appears there is no letting up. Recently, Forrester Research noted that there are now 7.3 billion mobile devices in a world where there are only 7 billion people.
"Mobile applications in the Enterprise may be a future vision for many companies, but mobile is a vision that is being realized much quicker than many had expected. What does the rise of mobile mean for the enterprise?
The global Enterprise Mobility (EM) market is expected to grow annually by 15 percent every year, eventually reaching $140 billion by 2020. By 2020 roughly 10-12 percent of the enterprise IT budgets will be spent on mobility, compared to less than 5 percent today. These numbers are based on a report by Nasscom in association with Deloitte.
Similarly,IDC is predicting that the biggest driver for new IT spending this year will be smart mobile devices, which include smartphones, tablets and eReaders. IDC expects that this segment will grow 20 percent and generate 57 percent of the IT industry’s total growth.
Industries where there are many customer interactions, like in banking, insurance and retail are seeing higher rates of Enterprise Mobile adoption. Mobile adoption is expected to also increase in government, healthcare and media.
The move to mobile is being fueled by mobile developers turning out applications for their businesses. Frost and Sullivan report that 82 percent of large North American businesses have already developed mobile apps for their employees. AndGartner is predicting that among in-house development projects, those that target smartphones and tablets will soon outnumber native PC projects by a ratio of 4-to-1." says Dick Weisinger of formtek.com.
Testing is critical in this process
JoshGalde 270005VQUH Marcações:  android object windows smartphone systems test smartphones store ctia os object-level app application keynote mozilla google device native blackberry automation mobile developers enterprise qa deviceanywhere scripting mobility html5 testing applications ios iphone level fragmentation developer firefox apps web 7.086 Visualizações
Recently Derek Britton of Micro Focus issued an article giving some great advice on how to develop one’s enterprise mobile strategy. As we have been discussing in recent posts, mobile is expanding exponentially and is putting even more pressure on IT teams to support these efforts. Derek covers some great ways to deploy a mobile strategy and support a mobile strategy in a cost-efficient way. In it he shared " The advent of the savvy end-user and the rising trend of “bring your own device” (BYOD) have immeasurably changed the way in which services must be provided by IT. As smart phone capabilities develop, so does the level of expectations for added functionality.
Businesses will find it impossible to ignore mobile if they wish to remain competitive in the next few years and must consider the most effective way to develop and adapt business applications to the needs of the mobile user.
The take-up of mobile technology will have “dramatic effect” on back-office IT systems, according to a study from Forrester Research. Modern users expect 24/7 mobile access to all the applications and online services that they would use on their desktop or laptop computer, visiting e-commerce sites, accessing their bank online, and more recently, loading their work applications. Yet, according to Forrester, “hidden costs and disruptions” are set to plague organizations that do not make appropriate pre-emptive action.
The Forrester Report suggests that mobile projects hide a variety of potential pitfalls as a result of infrastructure that is ill-prepared for exploding activity volumes. However, organizations need not think that embracing mobile will require a costly and complete overhaul of existing IT infrastructure to resolve these issues.
Businesses should consider re-using as much of their existing business applications and processes as possible in order to guarantee integrity, continuity and security of service for the future. Potential threats to the infrastructure of exploding activity volumes can be mitigated by making smart choices about application provision and workload management, to relieve pressure and offer a more cost- effective and viable solution to adopt mobile.
So what should businesses be doing to embrace mobile in a cost- efficient fashion? There are several steps that businesses can take to ensure that their IT infrastructures are prepared for the mobile explosion:
Re-use and adapt
All too often businesses approach mobile by developing new applications when in fact they could simply re-use and adapt existing, core back-end applications. The benefit of this approach is that costs are reduced and the existing infrastructure is not compromised.
While many may not consider COBOL for adapting business applications to support mobile use, its simplicity and therefore adaptability, makes this programming language, which accounts for approximately 70% of all critical business processes, the perfect candidate to take IT into the mobile era. With tools such as Visual Studio or Eclipse, developers are able to modernise applications to support new mobile applications across a wide number of technical platforms. COBOL can be used in each instance to efficiently deliver business services and their supporting data from the back-end to the user. The benefits of re-using COBOL systems rather than re-writing them are numerous and include a faster delivery of IT service, at lower cost and risk, while retaining intellectual property and competitive advantage.
Thoroughly test your mobile apps
When undertaking a considerable project such as adapting to mobile, testing is one area that cannot afford to be compromised. However traditional testing practices can mean that projects can overrun on time as well as budget. By moving application testing for mobile, web and related back-end systems to a more cost- effective environment that is easy to use, testing phases are able to be completed much faster and more thoroughly without eating into mainframe power. These environments also lend themselves better to supporting test automation and performance testing needs.”
As Derek reinforced - the need to thoroughly test your mobile apps is critical and that doesn’t have to be expensive either. Automated testing can be done in many different ways and utilizing different formats for different stages of your testing. From functional testing to performance testing, ensuring that your customers experience the highest quality of app or website is contingent upon how well it’s developed, and tested. More on this topic to come so check back soon or follow our blog today!
JoshGalde 270005VQUH Marcações:  blackberry apps web application fragmentation testing smartphone test mozilla keynote automation object firefox scripting native app store google mobile windows level enterprise systems applications ctia mobility developer device html5 os object-level developers ios deviceanywhere iphone qa smartphones android 6.790 Visualizações
In a recent article by Chris Marsh of Yankee Group, he addressed the new partnership between HP and SAP to address enterprise mobile apps. The services are intended to help the clients improve employee productivity with mobile apps and turn customer interactions into revenue opportunities. In it he says “HP’s partnership with SAP is indicative of how complex the enterprise mobility ecosystem has become. HP has been building out its own enterprise mobility management portfolio recently releasing its Enterprise Cloud Services providing sync, share and store for mobile applications and has aspirations to offer a wider portfolio of managed services. On the other hand it cannot afford not to partner with SAP around its more mature portfolio. From SAP’s point of view, the more the merrier, and momentum is on its side. As it pivots to focus more of the SAP group’s services around impactful B2BC engagement for its own customers it will aim to carve out more value in the mobility ecosystem…”
Recently, Keynote announced a complete integration with SAP partner – Worksoft. Worksoft, the provider of next-generation test automation solutions in support of SAP® applications brings speed and agility to SAP software by automating end-to-end testing, not just for SAP, but everything it interacts with. Worksoft’s integration with Keynote’s DeviceAnywhere platform provides its customers with access to seamless mobile software testing given its tight integration with the DeviceAnywhere solution. The integration offers a true end-to-end mobile integration in which Worksoft customers have 24x7 access to test SAP apps on any mobile devices, platforms or OS from their Worksoft Certify® interface. All of the device capabilities are accessible through the Worksoft Certify Mobile Interface Extension™. There is no scripting required. The joint solution leverages the Worksoft Certify approach to creating business process automated tests. And no additional training required since existing Worksoft Certify users don't need to learn another tool and have complete access to Keynote's powerful DeviceAnywhere mobile device testing platform. Existing SAP customers interested in leveraging DeviceAnywhere services to support the extension can get more information here.
JoshGalde 270005VQUH Marcações:  os level smartphones fragmentation smartphone store apps blackberry systems iphone object app qa test device android applications firefox web keynote mobility mobile enterprise developer html5 ctia application deviceanywhere mozilla object-level testing automation developers native ios google windows scripting 7.279 Visualizações
Recently, Kerry Butters wrote an article on the advancement and future projections of mobile hybrid apps in the marketplace. This is something we have been hearing from our customers. While we aren’t finding that it is a one or the other approach (aka Native VS HTML5 view), we do see a continued need for hybrid app development as organizations struggle to provide the highest quality of app possible, with feature-rich experiences, combined with a stringent delivery system forcing them to meet certain requirements by the carriers and app stores.
In Kerry’s article she writes “According to the latest research from analysts at research firm Gartner, hybrid apps will be used in over 50% of mobile devices by 2016.
This is due to the growing use of HTML5-based web apps which unlike native apps, do not have to use multiple versions of an app for different devices. However, HTML5 with offline capabilities haven’t really come up to scratch, causing developers to consider using hybrid architectures.”
"The BYOD trend and the increased pressure on organizations to deploy mobile applications to accommodate mobile work styles of employees will lead businesses to manage a portfolio of mobile application architectures, and hybrid architectures will be especially well-suited to business-to-employee applications,” said Van Baker, research vice president at Gartner.
Gartner also predict that mobile devices will overtake PCs as the most common way to access the internet by the end of the year and by 2016, PC shipments are expected to be less than 50% of combined tablet and mobile shipments.
"The implications for IT is that the era of PC dominance with Windows as the single platform will be replaced with a post-PC era where Windows is one of a variety of environments that IT will need to support,” said Mr Baker.
It’s also thought that a wide range of internet-capable devices, including set-top boxes, smart TVs and wearable devices will become much more popular.
"While hybrid apps will be the majority of enterprise mobile apps, web technologies like HTML5 will make up the most commonly used languages for building mobile applications by 2015,” said David Mitchell Smith, vice president and Gartner Fellow.
"We recommend organizations are open to augmentations to the Web (such as hybrid Application Development) to deploy on mobile today, with the goal that more should be done without those augmentations after 2015,” said Mr. Smith.
"Organizations also need to continue to develop web technology skills, find the right uses for promising new technologies and approaches like HTML5, and deal with the uncertainty and speed of the consumer-driven mobile landscape. All the while it’s important to maintain IT governance while increasing productivity and usability.’”
A full copy of the report Predicts 2013: Portal and Web Technologies can also be found on the site.
JoshGalde 270005VQUH Marcações:  blackberry firefox store applications google level mobility os object iphone html5 apps smartphone smartphones fragmentation testing developers device mobile native developer web enterprise android deviceanywhere mozilla scripting keynote windows ctia test qa object-level ios application systems app automation 7.816 Visualizações
Object-level scripting for mobile web content acts on individual web elements at the code level. This means that you can record a script on one device, and play the exact same script back on another device regardless of the screen-size, manufacturer or operating system. Object-level scripting for native apps does the same thing for devices of the same platform while acting on native objects. Your scripts will be more resilient through UI changes, lowering maintenance costs. We also announced a faster, easier way to record those scripts. With the DeviceAnywhere Recorder even the newest member of your team will be able to quickly create scripts for web, native and hybrid applications. With DeviceAnywhere SmartObjects and the DeviceAnywhere Recorder, you will quickly develop scripts that can be used within short agile test cycles, saving time and automating tests without a large upfront investment.