Manual Testing Vs. Automated Testing – From A Tester’s Viewpoint:

1.jpg

In today’s business area and economy, sparing cash is the highest priority on the rundown for any organization.

Testing is an essential part of any effective programming venture. The type of testing (manual or computerized) relies on upon different components, including Project prerequisites, spending plan, the course of events, skill, and relevance.

Three imperative components of any project are time, cost, and quality – the objective of any effective project is to diminish the cost and time required to finish it effectively while keeping up quality yield. With concerns to testing goals, one write may fulfill this objective superior to the next.

automation-testing-vs-manual-testing

Manual testing is best suited to the following scenarios:

  1. Exploratory Testing: This testing requires the analyzer’s learning, background, diagnostic/consistent abilities, imagination, and instinct. The test is described here by inadequately composed detail documentation, and additionally a brief timeframe for execution. We require the human aptitudes to execute the testing procedure in this situation.
  2. Usability Testing: This is user-friendly testing in which we have to understand, effective, or advantageous the product or item is for the end users. Here, human observation is the most critical element, so a manual approach is ideal.
  3. Ad-hoc Testing: It is an absolutely unarranged technique for testing where the comprehension and knowledge of the analyzer are the main essential component.

Automated testing is best suited for the following scenarios:

  1. Regression Testing: Here, automated testing is suitable because of frequent code changes and the ability to run the regressions in a timely manner.
  2. Load Testing: It is the best way to complete the testing efficiently when it comes to loading testing.
  3. Repeated Execution: Testing which requires the repeated execution of a task is best automated.
  4. Performance Testing: Similarly, performance testing requires the simulation of thousands of concurrent users requires automation.

Check out – Some of the major key factors to create a test automation framework.

Final Words:

After knowing all advantages and disadvantages of manual and automation testing, it is easy to choose that which type of testing is useful in a particular situation. For excellence software testing, both testing methods are required and both should be studied wisely because those values describe the core of Software QA.

 

 

 

Introduction to JMeter & How to View JMeter Test Results in Real-time?

What is JMeter ?

testng

The Apache JMeter is completely Java open source software. It was first developed by Stefano Mazzocchi who was working for Apache Software Foundation, designed to load test functional behavior and measure performance. You can use JMeter to measure the performance of variety of services or web applications.

Read More Here at http://www.bugraptors.com/introduction-jmeter-view-jmeter-test-results-real-time

How to select the Test Management Tool for Manual and Automated Testing?

Test Management is the process of tracking test cases, executing and documenting tests. A test management tool is used by QA teams and Testers to manage manual or automated tests that were earlier designed by stakeholders or testers(it is usually based on the necessities for a software project).

image-bug

It allows us to define complex test scenarios and enable teams to test software against multiple configurations(for example, multiple operating system versions). Advanced tools also allow you to track milestones, provide ways to view statistics and to view detailed reports of recent test activity.

Read More Here at http://www.bugraptors.com/select-test-management-tool-manual-automated-testing

What does the future holds for Internet of Things (IoT) Testing?

The Internet of Things could be the biggest software development and testing opportunity of all time.

IOT

 

Though devices such as tablets, phones and wearables may already seem global, the IoT which is a vast, networked array of sensors and embedded systems. It can eventually scale-down all of them in its global reach and number of services and applications.

Read More Here at http://www.bugraptors.com/iot-testing-future

How to Reproduce a Non Reproducible Bug

In our day-to-day life we all have various tasks to complete. Some of them are easy and the remaining is counted as Challenges. A software defect once found should be reproducible so that the tester can report with conviction, developer can fix with ease and the Quality Assurance (QA) team can close with confidence.

Types-of-Software-Testing

Being a software tester, we also face some challenges, such as Non-Reproducible bugs. Bugs which are not easy or cannot be reproduced again are termed as Non-Reproducible bugs which we often find harder to isolate and to get them fix becomes a difficult task.

Read More Here at http://www.bugraptors.com/non-reproducible-bug.

Why Your Website Should Be Responsive?

A responsive design responds to different display sizes by changing the size and layout depending on the device.

Why-Your-Website-Should-Be-Responsive

The main benefit is that mobile users will receive essentially the same experience of your website as your desktop visitors.

Responsive web design is becoming gradually more popular and many large companies have started to take this approach. Near the end of 2012 Microsoft released a redesign of their commercial website.

Read more at http://www.bugraptors.com/why-responsive-website.

Sanity Testing and Its Importance

Sanity Testing: Sanity Testing is a part of Regression testing . It is performed by the test team to do some basic testing  when they don’t have enough time to test the whole application. It is used to determine if all the features and functionality of an application is still working fine after a minor change or not. Sanity testing is performed to make sure that all the errors or bugs have been removed and there are no more issues  introduced due to  recent changes made within an application. It is performed when Smoke testing is done , accepted by QA team for further testing and verifies the major functionality with finer details.
It is usually unscripted and helps to identify the dependent missing functionality. It is  narrow and deep testing that focuses on one or a few areas of functionality. When there are some minor issues within the software and a new build is obtained after fixing the issues then instead of doing complete regression testing sanity is performed on that build. Sanity testing helps to avoid the wastage of time and cost if the build is failed. Sanity testing helps to check that after minor fixes done in a small section of code, the functionality is working as expected & not breaking related functionality .

When we Perform Sanity Testing?
Sanity testing is performed when development team needs to know quick state of the product after they have done changes in the code or there is some controlled code change in a feature to fix any critical issue, and stringent release time-frame does not allow complete regression testing.

Importance of  Sanity Testing

1. Sanity testing makes the tester confident about the functionality of an application.
2. Sanity testing assures that the part of the system or methodology works roughly as expected.
3. Using sanity testing the testers makes sure that the basic functionality of an application is working fine and the proposed functionality works roughly as expected.
4. By performing sanity testing on a Mobile Device Testing will be sure that the application will be working fine on other mobile devices having the same operating system.
5. Sanity testing is not documented and thus it saves time and is easy to perform.
6. Sanity testing gives a rough idea of the functionality of the application and the number of uncertainties in the application due to bug fixes.
7. Sanity testing is beneficial when the time for a particular project is limited and tester has already checked the project in detail.
8. Sanity testing does not require many testers and thus saving testing efforts.
9. Gives a quick state of the product to the developers after they have done changes in the code.