Subscribe to our Blog

Your email:

Current Articles | RSS Feed RSS Feed

Setting up the IBM Notes Application Testing Environment

 
IBM Notes Application Testing Environment

October 17, 2014 

As we mentioned in a previous blog post, Tips for IBM Notes and Domino Application Testing, testing IBM Notes applications is important to verify that applications function as designed and bugs don’t make it into production. Testing ensures the level of quality for an application falls within the acceptable range for your organization, and guarantees the ultimate success of the application once it’s deployed to the user community.

Before you start testing, you should understand the different application testing types. The testing activities themselves should be broken down into at least two distinct phases of testing.

  • Smoke Testing: The goal of smoke testing is to ensure the application is ready for testing. It’s a limited form of testing that can cover things that could normally break or be done incorrectly during the build process. For example, the agents not being signed correctly would prevent any testing from taking place.
  • Regression Testing: Regression testing is a more in-depth testing procedure that ensures previously working code has not broken.

Tips for IBM Notes and Domino Application Testing

 
IBM Notes and Domino Application Testing

October 15, 2014

To verify that IBM Notes and Domino applications function as designed, some level of testing is required. Without a concise policy defining what level of testing is required, there’s a much greater risk that bugs will make it into production. When bugs start impacting the end users of software, to any degree, you’ll quickly start to erode user confidence in the application as well as affect the ROI of the IBM Notes investment.

An important point to remember is that all software has bugs. It’s impossible to find and fix every possible bug in an application. Attempting to do so will mean you’ll never release the application. The goal of testing is to ensure that the number of bugs falls to a level that’s considered acceptable for a particular application.

The purpose of an IBM Notes application testing policy is to outline the process for measuring the quality of developed applications. By ensuring the level of quality for an application falls within the acceptable range for your organization, you can ensure the ultimate success of the application once it’s deployed to the user community.

Unplugged Developer Assistance Program for IBM Notes App Mobilization

 
Unplugged Developer Assistance Program for IBM Notes App Mobilization

October 10, 2014

At Teamstudio, we like to keep things fair and honest. That’s what you’ll find when you learn about our new Unplugged Developer Assistance Program (UDAP) for IBM Notes app mobilization.

We know that lots of organizations like to develop and mobilize their own IBM Notes and Domino applications. We get that it may be cheaper for them to use their own personnel, and not hire someone from a rent-a-developer shop or even Teamstudio. But everyone also knows that developing any kind of application can be tricky or even difficult at times. Wouldn’t it be much easier if you had a team of experts on-call to help with that nasty little bit of code that just will not work for you? Of course it would! We can and want to be there to help.

Our team of skilled IBM Notes developers is available to you for any coding issues that you may face when developing your Teamstudio Unplugged application. Developing an Unplugged application isn’t hard, but knowing that, should you run into an issue, you have the attention of someone who has already done what you are trying to do, is willing to help, share their skills, and give you advice along the way should be worth its weight in gold.

Like I said earlier, we like to be fair and honest. That’s why the entry cost to this program is really, really low. The way it works is designed with you in mind, too. Let me explain that for you in a little bit more detail.

4 Business Continuity Lessons Learned from the H1N1 Pandemic

 
Business Continuity Lessons from H1N1

October 8, 2014 

In April of 2009, the H1N1 virus was detected in a 10-year old in California. With direct lineage from Eurasian and North American swine (pigs), the virus is known as influenza Type A H1N1, or Swine Flu. After the virus was resistant to two of the more popular treatments, the U.S. was put on alert and the virus was deemed to be a public health emergency. Immediately, the Center for Disease Control took several business continuity measures in the face of the pandemic. 

In the end, the CDC estimated the H1N1 virus resulted in 12,469 deaths from April 12, 2009 to April 10, 2010 in the United States. While the H1N1 pandemic caused thousands of deaths, it also taught several important business continuity management (BCM) lessons that can be used in preparation for new pandemics. The following business continuity lessons from the H1N1 pandemic can be applied to today’s current Ebola outbreak in West Africa, and future pandemics to come. Some of the things we learned from H1N1 include:

XControls: Cards-based UI for Mobile and Desktop XPages Apps Released

 
Desktop view of a sample XControls application

October 7, 2014

This week we have released a new project on OpenNTF called XControls. If you’ve seen our previous project, the Unplugged Custom Controls, then hopefully the problems we’re trying to solve will be familiar, but with this new project we’re expanding the scope of what we cover. The XControls project allows you to quickly create XPages applications by dragging and dropping custom controls into your XPages, but now when you do that, the applications you create will work on desktop browsers, mobile browsers, and Teamstudio Unplugged.

Depending on how you view the application, the layout will automatically reconfigure itself to best fit the device. In the screen shots below, you can see the same page being viewed in the desktop, iOS, and Android:

How to Deliver Quality IBM Notes Apps with an Automated Build Process

 
How to Deliver Quality IBM Notes Apps with an Automated Build Process

October 3, 2014

To stay ahead of the competition and fine-tune your operation to meet customer needs, you must continually improve business critical applications and the processes that support them. Whether it’s enhancements to existing applications or new product applications, one of the primary and most error prone processes in the IBM Notes application development lifecycle is the process for deploying applications to the end user community.

To minimize the costs and risks associated with putting applications into production, the ideal solution is to automate the deployment process as much as possible.

The purpose of this blog post is to focus the development and administration teams’ efforts in delivering a stable application every time a new release is built. By employing a repeatable, documented, effective, and potentially automated build process, these teams can ensure that high quality applications are delivered to their users. 

A policy for application delivery should address all new applications and application enhancements that are moved into a new environment, i.e. test, staging or production. Applications should be moved via a documented and approved process that encompasses all required procedures to properly prepare the application for the next environment. The process requires at least two members of the deployment team to perform two different stages of the process. This will ensure segregation of duties and completion of all tasks.

How to Document Your Current IBM Notes Build Process

 
How to Document Your Current IBM Notes Build Process

October 1, 2014

Control of existing deployment processes and procedures may not be documented, leading to deployment errors when IBM Notes applications are rushed through an undisciplined deployment process. Missed steps along the way reduce the quality and consistency of business applications, and can often result in a significant amount of end user and help desk troubleshooting.

An effective build process should:

3 Points of View on the Apple + IBM Enterprise Mobile Alliance

 
Apple + IBM Enterprise Mobile Alliance

September 26, 2014

On July 15, 2014, Apple and IBM announced their global partnership to develop enterprise mobile business applications for iPhone and iPad. Some say the deal, dubbed IBM MobileFirst for iOS, will fail miserably just like their previous attempts at working together, while others see the potential and believe the alliance will facilitate a Jetson’s-like reality. Whether the partnership will be successful or bust, there’s no doubt this is a significant announcement and there will be a ripple effect in the software industry. Here’s the Apple + IBM story from all angles.

Business Continuity Tips for Pandemic Preparation

 
Business Continuity Tips for Pandemic Preparation

September 24, 2014

Recently, business continuity practitioners along with the world have been watching in a state of panic as the Ebola virus ravages West Africa. According to CNN, more than 2,400 people have died from this outbreak in Guinea, Liberia, and Sierra Leone, and the number of new cases is increasing exponentially.

Ebola is one of the most deadly viruses known to man with a fatality rate that can reach up to 90%. Individuals can become infected if they come into direct contact with the blood or other bodily fluids of an infected person. Coming into contact with needles or other objects that may have penetrated an infected person’s skin is also a means of transmission. People infected with Ebola may begin having symptoms related to the common flu, that turn into more severe symptoms as days pass. The mortality rate of Ebola is extremely high, but can be significantly reduced if caught in the very early stages. An infected person can remain infectious as long as their bodily fluids contain the virus, which has been reported to be as long as two months after the initial onset of illness.

Disease epidemics such as Ebola, H1N1, and SARS continue to occur. Use the following tips to prepare your business continuity plan for epidemics such as these.

5 Reasons to Care about a Business Continuity Plan

 
Business Continuity Plan

September 19, 2014

Today's businesses face plenty of challenges and risks. Some are predictable, and some are not. According to AT&T’s 2013 business continuity study, 13% of companies with revenues of more than $25 million don’t have a business continuity plan in place. The 87% of businesses with a plan for recovering from an internal or external threat understand it’s better to be prepared than it is to be unprepared and faced with a lengthy or insurmountable recovery period. A business continuity plan may seem daunting, complicated, and even unnecessary to some business owners. However, a plan is a crucial component to recovering from a disaster. Here are five reasons why every business should care about advancing their business continuity and disaster recovery plans.

 

All Posts