Learn Manual Testing Step by Step Guide, Manual Interview Questions, Manual Testing Job




Manual Software Testing

This stage is carried out in two modes as a complete package or as a increment to the before this packages ..


This type includes the testing of the Software manually i.e. without using any automated tool or any script. In this type the tester takes over the role of an end user and test the Software to identify any un-expected behavior or bug. There are different stages for manual testing like unit testing, Integration testing, System testing and User Acceptance testing.


Testers use test plan, test cases or test scenarios to test the Software to ensure the completeness of testing. Manual testing also includes exploratory testing as testers explore the software to identify errors in it.


Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases.


Automate

it is not possible to automate everything in the Software; however the areas at which user can make transactions such as login form or registration forms etc, any area where large amount of users. can access the Software simultaneously should be automated.


Furthermore all GUI items, connections with databases, field validations etc can be efficiently tested by automating the manual process.


Automation is done by using a supportive computer language like vb scripting and an automated software application. There are a lot of tools available which can be use to write automation scripts. Before mentioning the tools lets identify the process which can be used to automate the testing:


There are several stages. They are:

Automation testing

Automation testing which is also known as Test Automation, is when the tester writes scripts and uses another software to test the software. This process involves automation of a manual process. Automation Testing is used to re-run the test scenarios that were performed manually, quickly and repeatedly.


Unit Testing

Unit tests enable refactoring as well. After each small change the unit tests can verify that a change in structure did not introduce a change in functionality. This initial stage in testing normally carried out by the developer who wrote the code and sometimes by a peer using the white box testing technique. Unit Tests provide a safety net of regression tests and validation tests so that you can refactor and integrate effectively. As they say at the circus; never work without a net! Creating the unit test before the code helps even further by solidifying the requirements, improving developer focus, and avoids creeping elegance. Unit tests are released into the code repository along with the code they test. Code without tests may not be released. If a unit test is discovered to be missing it must be created at that time.


Integration Testing

Most of the time black box testing technique is used. However, sometimes a combination of Black and White box testing is also used in this stage.  Integration is the testing process in software technology.  To verify that when two or more modules are interact and produced result satisfies with its original functional requirement or not. Integrated

testing is fall in Black box testing. Integrated testing will start after completion of unit testing.  software testing engineer is performing integration testing.

There are main three types of integration testing.


1. Big Bang


2. Top down


3. Bottom up

Software Testing


After the integration has been tested, software testers who may be a manual tester or automaton perform software testing on complete software build. This Software testing consists of two type of testing:


1. Functional (to check whether SUT (Software under testing) is working as per the Functional Software Requirement Specification. This is performed using White Box testing techniques like BVA, ECP, Decision Table, Orthogonal Arrays. This Testing contains four Front-End testing(GUI,Control flow,Input Domain, Output or anipulation) and one Back-End testing i.e. Database testing.


2.Non-Functional Testing /System Testing/Characteristics Testing(to check whether SUT is working as per the NFRS, which contains characteristics of the Software to be developed like Usability, Compatibility, Configuration, Inter System Sharing, Performance, Security)
System Testing

is the testing of behavior of a complete and fully integrated software product based on the software requirements specification (SRS) document. In main focus of this testing is to evaluate Business / Functional / End-user requirements. In this stage the software is tested from all possible dimensions for all intended purposes and platforms. In this stage Black box testing technique is normally used. System Testing enables you to test, validate and verify both the Application Architecture and Business requirements. System Testing is performed on staging server which is similar to production server. So this means you are testing software application as good as production environment.


User Acceptance Testing

The object of this testing is to verify correctness of the module. The purpose of unit testing is to check that as individual parts are functioning as expected. Basically Unit testing is typically carried out by the developer.  This testing stage carried out in order to get customer sign-off of finished product. A 'pass' in this stage also ensures that the customer has accepted the software and is ready for their use.


Release or Deployment Testing

Onsite team will got to customer site to install the system in customer configured environment and will check for the following points:


1. Whether SetUp.exe is running or not.

2. There are easy screens during installation


3. How much space is occupied by system on HDD

4. Is the system completely uninstalled when opted to uninstall from the system.


GUI (Graphical User Interface) Testing



A testing framework generates user interface events such as keystrokes and mouse clicks, and observes the changes that result in the user interface, to validate that the observable behavior of the program is correct. What to automate, when to automate, or even whether one really needs automation are crucial decisions which the testing (or development) team must make. Selecting the correct features of the product for automation largely determines the success of the automation. Automating unstable features or features that are undergoing changes should be avoided.
 

Learn Manual Testing Step by Step Guide, Manual Interview Questions, Manual Testing Job

Here Some Important and hot list of Manual Software Testing Questions are provided. Just click on these links and find your expected answers there. All types of questions are included in this list


  9. Give the Definition of Test Case Development Formalities. 


No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts