Types of Software Testing

Unit Testing | Integration Testing | FunctionalTesting | System Testing | Stress Testing | Performance Testing | Usability Testing | Acceptance Testing | Regression Testing | Beta Testing

Types of Software Testing

Unit Testing | Integration Testing | FunctionalTesting | System Testing | Stress Testing | Performance Testing | Usability Testing | Acceptance Testing | Regression Testing | Beta Testing

Types of Software Testing

Unit Testing | Integration Testing | FunctionalTesting | System Testing | Stress Testing | Performance Testing | Usability Testing | Acceptance Testing | Regression Testing | Beta Testing

Types of Software Testing

Unit Testing | Integration Testing | FunctionalTesting | System Testing | Stress Testing | Performance Testing | Usability Testing | Acceptance Testing | Regression Testing | Beta Testing

Types of Software Testing

Unit Testing | Integration Testing | FunctionalTesting | System Testing | Stress Testing | Performance Testing | Usability Testing | Acceptance Testing | Regression Testing | Beta Testing

Monday, 10 November 2014

How to create and run FTP request script in jmeter


How to create and run FTP request script in jmeter?







Building an FTP testplan is a very easy task. You just need to know the ip, username and password of

remote machine.






Steps:






1. The first step to open jmeter, and add a thread group.


2. Now in thread group define users or number of threads you want to run your test.


3. Add FTP request default under thread group (Thread Group>>Add>>Config Element>>FTP request defaults), and enter the server/remote machine’s ip or domain. Port number is non-mandatory; if you will provide it jmeter will use its default port.














4. Now add FTP request under the thread group (Thread Group>>Add>>Sampler>>FTP Request).













5. In FTP request, you need to provide, the remote machines ip, and port number if you want.


6. In Remote file you need to provide the complete path of the file you want to copy or where you want to write your data.


· E.g. home/directory/file1.txt


7. So after providing the file path, the complete accessing path of remote machine will be like Server IP/ home/directory/file1.txt or192.168.10.12:8080://home/directory/file1.txt.


8. Now provide the local file path, from where you are transferring the file or to where you are copying or writing the data.


· E.g. C:\Users\Marvin\Desktop\MyFile\file2.txt


9. The file ext of remote and local file should be same, else it will not be able to write or read the data. Transferring the file means you are copying the content/data of one file to another.


10. The get (RETR) radio button will be checked if you want to retrieve the data from remote machine.


11. Put (STOR) radio button will be checked if you want to transfer the data to remote machine.


12. Save file to response enables you to store your data in response, so that when you will run the test you will be able to see the exact data in your listener (view result tree).


13. Last provide the correct username and password of your remote machine.










14. Add a listener (view result tree or table) to your thread and run the test.

Wednesday, 5 November 2014

Test Cycle Closure



Call out the testing team member meeting & evaluate cycle completion criteria based on Test coverage, Quality, Cost, Time, Critical Business Objectives, and Software. Discuss what all went good, which area needs to be improve & taking the lessons from current STLC as input to upcoming test cycles, which will help to improve bottleneck in the STLC process. Test case & bug report will analyze to find out the defect distribution by type and severity. Once complete the test cycle then test closure report & Test metrics will be prepared. Test result analysis to find out the defect distribution by type and severity.

Entry Criteria
Activities
Deliverable
1.      Test case execution is completed.

2.      Test case Execution report.

3.      Defect report.
1.      Evaluate cycle completion criteria based on Test coverage, Quality, Cost, Time, Critical Business Objectives, and Software Prepare test metrics based on the above parameters.

2.      Prepare Test closure report.

3.      Share best practices for any similar projects in future.
1.      Test Closure report

2.      Test metrics

Test Execution



Once the preparation of Test Case Development and Test Environment setup is completed then test execution phase can be kicked off. In this phase testing team start executing test cases based on prepared test planning & prepared test cases in the prior step.
Once the test case is passed then same can be marked as Passed. If any test case is failed then corresponding defect can be reported to developer team via bug tracking system & bug can be linked for corresponding test case for further analysis. Ideally every failed test case should be associated with at least single bug. Using this linking we can get the failed test case with bug associated with it. Once the bug fixed by development team then same test case can be executed based on your test planning.
If any of the test cases are blocked due to any defect then such test cases can be marked as Blocked, so we can get the report based on how many test cases passed, failed, blocked or not run etc. Once the defects are fixed, same Failed or Blocked test cases can be executed again to retest the functionality.
Entry Criteria
Activities
Deliverable
1.    Test Plan or Test strategy document.

2.    Test cases.

3.    Test data.
1.      Based on test planning execute the test cases.

2.      Mark status of test cases like Passed, Failed, Blocked, Not Run etc.


3.      Assign Bug Id for all Failed and Blocked test cases.

4.      Do Retesting once the defects are fixed.


5.    Track the defects to closure.
1.      Test case execution report.

2.    Defect report.

Test Environment Setup



Setting up the test environment is vital part of the STLC. Basically test environment decides on which conditions software is tested. This is independent activity and can be started parallel with Test Case Development. In process of setting up testing environment test team is not involved in it. Based on company to company may be developer or customer creates the testing environment. Mean while testing team should prepare the smoke test cases to check the readiness of the test environment setup.
Entry Criteria
Activities
Deliverable
1.      Test Plan is available.

2.      Smoke Test cases are available.


3.    Test data is available.
1.      Analyze the requirements and prepare the list of Software & hardware required to set up test environment.

2.      Setup the test environment.

3.    Once the Test Environment is setup execute the Smoke test cases to check the readiness of the test environment.
1.      Test Environment will be ready with test data.

2.    Result of Smoke Test cases.

Test Case Development



The test case development activity is started once the test planning activity is finished. This is the phase of STLC where testing team write down the detailed test cases. Along with test cases testing team also prepare the test data if any required for testing. Once the test cases are ready then these test cases are reviewed by peer members or QA lead.
Also the Requirement Traceability Matrix (RTM) is prepared. The Requirement Traceability Matrix is an industry-accepted format for tracking requirements where each test case is mapped with the requirement. Using this RTM we can track backward & forward traceability.

Entry Criteria
Activities
Deliverable
1.      Requirements Documents (Updated version of unclear or missing requirement).

2.      Automation feasibility report.
1.      Preparation of test cases.

2.      Preparation of test automation scripts (if required).

3.      Re-requisite test data preparation for executing test cases.
1.      Test cases.

2.      Test data.

3.      Test Automation Scripts (if required).