Manual vs. Automation – Let the Battle Begin

Testing is like a stage production showcasing the standard of work for an organization in the market. It is a vast, and generally overlooked, part of the software development process which can be considered  a change agent who highlights risk early to provide efficiencies in the way that we develop and deploy our software. It is broadly categorized into two methods: Manual and Automated Testing.

With more organizations understanding the essential role testing plays in quality software production, they are still discovering the best way to examine the quality of their software.

So what is the difference between Manual and Automated Testing?

Both manual testing and automation have their own benefits and setbacks and its worth knowing when to use which type of an improved outcome.

Manual testing reflects its definition and usage.  Testing is conducted by humans while with automation, the tester needs the support of tools to perform the tests. Both the methods cover all testing methods like black box, white box, load testing, etc. Among these methods, some case better performed manually while others work best in automation, it all depends on the situation or the requirement of the software. Trends show that organizations are keeping eye on automation but that doesn’t mean manual is going anywhere anytime soon.

advantages-disadvantages-test-automation

Let’s take a look at the pros and cons  each:

Automation Testing Track up’s

Automation has advantages over manual in that it is fast test execution reliable, repeatable, and programmable etc. In automated testing, test execution speed is faster – like a racing car – which reduces manpower, time, and efforts deployed during the testing process. It also plays an important role in long-term projects and is suitable for regression testing purposes. Let’s use the example of filling in the same registration forms manually and repeatedly. In different cycles or iterations, this becomes inefficient since manual testing does not offer code reusability. Thus, the complete code needs to be re-written in the case of a change in resources. If we compare this with automation, any team member can use the test case anytime. Additionally, the cost of tools with fewer resources is less expensive than having a large team for the manual testing process required to complete the same tasks. The aspect of automation is not just to reduce testing, but it’s also productive and results-oriented.

Manual Testing Track up’s

So does this mean the end of manual testing? Does it have a future?

There are still stacks of technologies which require manual testing where automation fails. Applications which are based on touch technologies, such as Kindle, iPad, Tablets etc. still require manual testing. GUI testing proves manual testing is preferable over automation. In the GUI, layout changes are difficult to test through automation because when you playback the recorded scripts any gestures or buttons which were available at the time of recording that were not found may cause the test scripts to not function properly. Also, with manual testing, a person can perform random testing that allows for the finding possible bugs.

Below is a chart of the differences.

Manual Testing

Automation Testing

Test run by a person Test runs through tools
The initial phase of testing without it automation would not possible Continuous part of manual testing
All the STLC phases like test planning, Executions, bug tracking, etc. is done successfully by human Hands In automation, we can do using various open source and licensed tools like Bugzilla, HP ALM, JIRA, etc.
Lower cost Higher cost
Time-consuming Takes less time
Difficult to do regression testing Regression testing simple with the help
of tools
More resources required to execute
test cases manually
Need fewer resources as testing is
done with the help of tools
Random testing can be performed to
track bugs
Can only test according to automated scripts
No programming skills are required –
a non-technical person can also do
manual testing
Programming skills are needed. Testers can program the complex tests to find
the bugs
Considered to be less reliable Considered to be more reliable
Low accuracy results High accuracy results
Difficult to do non-functional tests in manual testing Non-functional tests are effortless with
the help of tools

 

Who wins the battle?

So which is better Manual or Automation? They both have their benefits, so it depends on what testing approach is the best for the situation. Choosing the right approach gives you the right direction to achieve your goals as well as saving you time, result and efforts. The entire outcome of these tests comes when the right type of testing is applied in the right environment. Both testing approaches have their own benefits and drawbacks, but for software testing quality, you need to utilize both methods sensibly.

bot

Enter the Oracle Forms Extreme Mobile Makeover Contest

In a world where everything is at the tip of your fingers, why are your enterprise systems glued to your desktop?  Imagine if you could access and operate your Oracle Forms/EBS Systems from any location.  What if your Oracle Forms system was so agile and easy to adapt, that any business function performed in Oracle Forms could be included in a mobile application? What would you include in your mobile strategy?

How about …

  • Doing time reporting directly from your mobile device
  • Managing work orders and entering follow up actions in the field
  • Performing onsite inspections
  • Generating revenue with point of sale solutions

…all without redeveloping your Oracle Forms/EBS systems.

Now is the chance to see for yourself!

By using our solution, we can expose existing Forms applications to mobile without writing one line of code. That’s right!  No code and no need for redevelopment or migration of Oracle Forms.

Not possible?

It is.  And to prove how easy it is, we are hosting an extreme makeover mobile use case competition with our contest partner AuraPlayer.  Together we will select three companies to showcase a business case that is currently a legacy to mobile challenge.  This summer, we will develop a prototype mobile application for each of the three finalists free of charge (trial software licenses included).  The finalists’ applications will be presented at Oracle OpenWorld in San Fransisco in September 2016.  Find the full details here.

Want to enter the contest and see your Oracle Forms application on a mobile device? All you have to do is complete this application before Monday, June 20, 2016. Three finalist will be selected to get a prototype of their app developed, and exposure of their creative mobile vision at Oracle OpenWorld.

In addition, one winning finalist will be selected to receive: A free Samsung 6S Edge+ 

Sofbang Tech Team Tips Series: Configuring Database Cloud (DbaaS) with Java Cloud for Application Deployment

In this post of Tech Team Tips Series, I am going to show how to migrate existing ADF web application deployed on-premise WebLogic 12c to Oracle Java Cloud Service.

I will use an existing WebLogic 12c ADF sample web application for migration. Before deploying the application, it is essential to configure these important steps:

Create Schema in Database Cloud (DbaaS)

Configure Data source in JCS

I encountered few slips while configuring these pre-requisites at first time. The following is what I encountered and how you can avoid and/or troubleshoot these slips:

1. Schema Creation through SQL Developer:

a. The “ORA–65096” error:

SQL Error: ORA–65096: invalid common user or role name

The Cause: An attempt was made to create a common user or role with a name that was not valid for common users or roles. In addition to the usual rules for user and role names, common user and role names must start with C## or c## and consist only of ASCII characters.

b. The “ORA–6048” error:

 SQL Error: ORA–65048: error encountered when processing the current DDL statement in pluggable database PDB1
 ORA–01955: DEFAULT ROLE ‘CONNECT’ not granted to user
 65048.00000 - “error encountered when processing the current DDL statement in pluggable database %s”

The Cause: An error was encountered when executing a statement in one of the pluggable databases.

2. JNDI Creation Error from JCS WebLogic console.
a. Connection test failed. Error ORA–01045.

Error ORA–01045: User C##TEST lacks CREATE SESSION privilege; logon denied
 oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
 oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
 oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:391)

b. Connection test failed. Error ORA–01017:

Error ORA–01017: invalid username/password; logon denied
 oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
 oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
 oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:391)

Don’t worry about these errors, just follow the steps below to configure your cloud environment properly for smooth running.

Continue reading…

State & Local: Licensing and Permitting – A Streamlined Solution in Oracle PaaS

Licensing and permitting is a vital line of business to all state and local public sector entities throughout the world. Whether it is a business license, driver’s license, vehicle residential permit or any other license or permit, public sector departments have mastered the process of issuing, managing and tracking licenses specific to their domain. While the current processes may be down to a science, state and local organizations continue to deal with critical challenges of having to constantly do more with less.

Organizations are looking to modernize, consolidate or retire antiquated systems that are manual, paper intensive and require redundant, repetitive data entry. Our latest whitepaper dives deeper into the complexities associated with these challenges and provides a fresh perspective, along with best practices to streamline the licensing and permitting functions within an enterprise.

Read the whitepaper(PDF): State & Local: Licensing and Permitting