TEST PLAN (TEST FACTORS Vs TEST TECHNIQUE)

TEST

 

Test factors                          Vs                         Test technique

Test factor indicate testing issue topic. this test engineer's topic in our project testing team is following ECT of testing techniques 

 Authorization :- security testing 

 Access control :- security testing 

 Audit trial :-   Functionality testing 

 Continue of processing :- Integrating (programmer)

 Data Integrity :- I/P Domain Testing 

 Correctness of proceeding of O/P value and maipulation: Functionality testing 

Coupling :- Inter system testing 

Ease of use:- user inter face testing / manually support testing  

Ease of operation :- Insulation testing 

Portability compatibility/ configuration Testing

Performance :- load / stress/data volume testing 

Reliability :- Recover/stress testing 

Service levels :- S/W changes/ regression testing(by CCB)

Maintainable :- compliance testing 

Methodology :- compliance testing 

Whether the project team is following our enhancement standards.

read more...

SYSTEM TESTING PROCESS

System Testing process

     

SYSTEM TEST INITIATION

 

Generally the every organization system testing process is a starting with test initiation.

In this face project manager (or) test manager prepare test strategy documents. This document  defines requires testing approach to be followed by testing team.

A) components in test strategy :

1. scope & objective ;  the important of testing & their mail stones.

2. Business issues ;     cost allocation in between development process and testing process.

 

3. Test approach; list of test factors of test issues to be applied by testing team on corresponding S/W build. this selection is depending on requirement is that S/W build scope of the requirements and risk involve in our project testing .

4. Roles & responsibilities; the names of the job in testing team& their responsibilities.

5. communication & status Reporting; This required negotiation between every two consecutive jobs in our testing team.

6.  Test automation and Testing tools; The purpose of automation & available tools in our organization.

7.   Defect Reporting & Tracking; The required negotiation between this testing team & development team to review and resolve defect during testing.

8. Testing Measurements and machines; To estimate quality, compatibility & status testing team uses a set of measurement & metrics.

9. Risks & Assumptions; The exemptions list of problems this solution to overcome.

10. Change & Configuration management;

11. Training Plan; The required number of training session for testing team. To understand customers requirement (or) business
logics.

12. Test deliverable; Names of test document to be prepared by testing team during testing 
     EX: test plans, cases, log, defect reports and same reports.

13. Test factors & testing issues; To define quality S/W, Testing use 15 issues (or) topics. these all topics are not mandatory in every project.

I. Authorization :- Validity of users 
II. Access Control:- permission of users use specific functionality
III.Audit trail:-  The correctness of metadata mean data about data
IV. Continuity of processing:- Integration of processing
V. Data Integrity :- correction of me/P value :- compose mail (interim of size & Time).
VI. Correction of O/P value and Manipulation :-
VII. Coupling :- coexisting with other S/W to share common resources.
VIII. Ease-of-use :- User friendly screen
IX. Ease of Operation :- Installation, an installation dumping, downloading, upload. 
X. Portability:- Run on different platforms 
XI. Performance:- speed of processing 
XII. Reliability:- Recover from abnormal situation 
XIII. Service Levels:- Orders of functionality are services to give to customer side people. 
XIV. Maintainable:- whether our S/W is time serviceable to customer site people(or) not.
XV. Methodology :- Testing factor on whether on testing team following predefined approach properly(or)not?

read more...

TESTING TERMINOLOGY

TESTING TERMINOLOGY

 

1.TESTING STRATEGY

 

It's a document and it does define the required testing approach to be followed by testing people.

 

2. TEST PLAN 

 

It's a document and its provides work allocation and in terms of schedule

3.TEST CASE

 

It does define test condition to validate functionality in team of completeness and correctness.

4.TEST LOG

 

It's defining the result of test case in team of passed (or) fail of exeution of  testing case application build.

5.ERROR-DEFECT(ISSUE)-&DEBUG

 a) A mistake in a coding is called error

 b) This mistake found by test engineer , during testing called DEFECT/ ISSUE

 c) This defect/issue review & accepted by development team to release is called BUG.

 

6. RE-TESTING

 

It's also known as data driven (or) iteration testing . test engineers repeat the same test on same application build with multiple I/P values . this type of test repetition is called Re-testing.

 

7. REGRESSION 

 

The Re-execution of scheduled test cases on modified build to ensure, bug-fix work without any effect is called regression test.

 

 

 

 

 

 

 

 

 

read more...

Mostly Using Test Cases

TEST CASES 

 

Mostly Using Test Cases

1.All mandatory fields should be validated and indicated by asterisk(*)symbol.

 

2. Validation error messages should be displayed properly at correct position

3. All error messages should be displayed in same CSS style (e.g. using red color)

4. General confirmation messages should be displayed using CSS style other then error messages style (e.g. using green color)

5. Tool tips text should be meaningful

6. Dropdown fields should have  first entry as blank or text like 'select'

7. Delete functionality for any record on page should ask for confirmation 

 

8. Select/deselect all records options should be provided if page supports record add/delete/update functionality

 

9. amount values should be displayed with correct currency symbols 

 

10  . Default  page sorting should be provided

11. Resent button functionality should set default values for all fields

 

12. All numeric values should be formatted properly 

 

13. Input fields should be checked for max field value. input values greater than specified max limit should not be accepted or stored in database

   

14.Check all input fields for special characters 

 

15. Field labels should be standard e.g. field accepting user's first name should be labeled properly as 'first name'

 

16. Check page sorting functionality after add/edit/delete operations on any record 

 

17. Check for timeout functionality. Timeout values should be configurable. Check application behavior after operation timeout

 

18. Check cookies used in an application

 

19. Check if downloadable files are pointing to correct file paths

 

20.All resource keys should be configurable in config files or database instead of hard coding 

 

21.  Standard conventions should be followed throughout for naming resource keys 

 

22. Validate markup for all web pages (validate HTML and CSS for syntax errors) to make sure it is compliant with the standards 

 

23. Application crash or unavailable pages should be redirected to error page 

 

24. Check text on all pages for spelling and grammatical errors 

 

25. Check numeric input fields with character input values . proper validation message should appear 

 

26. Check for negative numbers if allowed for  numeric fields 

27. Check amount fields with decimal number values

28. Check functionality of buttons available on all pages 

29. User should not be able to submit page twice by pressing submit button in quick succession.

30. Divide by zero errors should be handled for any calculations 

31. Input data with first and last position blank should be handled correctly

 

read more...

UNIT TESTING

Unit testing is 4 types 

 

                    1. Basis path Testing

                    2. Control structure Testing

                    3. Program Technique Testing

                    4. Mutation Testing

 

 1. Basis path testing :- programmer is verifying whether a programmer is running or not. In basis path testing, programmer are following the below procedure to test complete programme.

>  Draw flow diagram for that programme

> Calculate on of independent paths in that programme(geometric complexity) .

> Run that programme more than are time to cover all independent paths in that programme.

 

2. control structure testing :- programmers concentrate on the correctness and completeness of  the corresponding programme outputs. they are checking every statement including 'if' conditions for 'loops' memory allocations. 

 

3. program Technique Testing :- programmers verify the execution speed of corresponding program. In this testing , programmer is taking the help of 'monitors' and "properties". if the programme without disturbing the functionality.

 

4. mutation testing  :- A mutation is a small change in program . mutations are introduced into programs to test the completion of tests on that program are probably incomplete.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

chakrapani

read more...

Introduction software testing

                                    Introduction :-

 The  software engineering process represents the tasks including physical and logical requirements as a story ,team software project . Software development process is a complex process, which requires careful planning and execution to meet the goals . 

 

                    Sometimes a developer must react quality hinders fast-paced software development, as many testing cycles are necessary to ensure quality products .

 

                 As the complexity of software increases , the demand for having a solid and systematic development process also increases to ensure a quality product that meets customer requirements.  

 

 

 

 

 

 

 

 

 

 

read more...

Software Testing Tutorial

                                                manual Testing 

 

Testing Introduction

UNIT TESTING

TESTING TERMINOLOGY

 

 

 

 

 

 

 

 

read more...

LOG/REFERENCE/UI-ELEMENI/ROllUP PANE in Selenium IDE

Log :-

 when you run your test case,error messages and information massages showing the progress are displayed in this pane automatically, even if you do not first select the log tab. These massages are often useful for test case debugging. Notice the clear button for clearing the log. 

 

 

  Reference :-

The reference tab is default selection whenever you are entering or modifying selenese(selenium ide script) commands and parameters in table mode . in table mode , the reference pane will display documentation on the current commend. When entering or modifying commands, whether from table or source mode , it is critically important to ensure that the parameters specified in the target  and value fields match those specified in the parameter list in the reference pane. The number of parameters provided must match the number specified, the order of parameters provided must match the order specified, and the type of parameters provided must match the type specified .If there is mismatch in any of these three areas, the command will not run correctly.

 

UI-Element and rollup

While the reference tab is invaluable as a quick reference, it is still often necessary to consult the selenium reference document.

 Detailed information on these two panes (which cover advanced features ) can be found in the UI-Element Documentation  on the help menu of selenium-IDE.

 

 

 

read more...

Selenium IDE

Selenium IDE :- (Integrated Development Environment)

➻ Selenium IDE was developed by Shinya Kasatani
➻ Integrated means To make into a whole by bringing all parts together (or) To make part of a larger unit .
➻ selenium IDE is a creating developing environment means jest you record and play back your test cases
➻ this tool provides to record,Edit and debug tests
➻ currently IDE is available as a plug-in Extension for Fire fox browser
➻ IDE is available only fire fox is a default browser
➻ It is not only a time-saver,but also an excellent way of learning selenium script syntax.
➻ In selenium IDE the script will run only in HTML format
➻ selenium IDE is very easy to use in testing automation tool

when to use Selenium IDE :-

➻ We can use the the tool to check the compatibility of the application with selenium
➻ We can use the tool to generate script on the web objects which we not able to identify the object properties and understand how the tool can identify which properties it uses.

:-

read more...

Why Automation ? (Advantages of Automation)

Advantages of Automation :-

⇛ Perform regression testing
⇛ Test execution can be completed faster
⇛ Reduce cost to the company(CTC)
⇛ Testing is consistent and effectiveness
⇛ Reusability of Scripts
⇛ Reporting is Easy
⇛ Reduce cost of testing

When to go Automation :-

⇛ Application should be stable 

          STABLE :- majority of the cases should be pass and no blocker bugs should                                      report in  reporting tools
⇛ Identify the scope for automation
⇛ Clint approval based on budget

Automation Testing conclusion :- 

⇛ Automation Testing is not passable 100% it's like performance testing ,regression    testing load and  stress testing when you can have chance of passable to reaching          near to 100%  automation testing.
          Exp:- when we sending massage  application throw mobile it must be done                               manually.

 ⇛Automation  Testing Process :-

read more...

Installation Selenium IDE

Installation :-

➫  Lauch fire fox browser, if not available Download fire fox browser and install

➫ go to selenium IDE Downloads page click 

➫ Firefox will protect you from installing Add-ons from unfamiliar locations , so you will need to click allow to proceed with the installation.

➫ After install selenium IDE once need to restart the fire fox browser and follow instructions 

➫ After firefox reboots you will find the selenium-IDE listed under the firefox Tools menu.

➫ To run the selenium-IDE,it opens as follows with an empty script-editing window and a menu for loading, or creating new test cases. 

Toolbar :-

➫ The toolbar contains buttons for controlling the execution of your test cases,including a step feature for debugging your test cases. the right-most button, the one with the red-dot,is the record button.

1. Speed control:- controls how fast your test case runs.

2. Run All :- runs the entire test suite when a test suite with multiple test cases is loaded.

3. Run :- puns the currently selected test. When only a single test is loaded this button and the all      button have the same effect.

4. pause/resume:allows stopping and re-starting of a running test case.

5. step:allows you to "step" through a test case by running it one command at a time. Use for debugging test cases.

6. TestRunner mode:allows you to run the test case in a browser loaded with the selenium-core testRunner. Thetestrunner is not commonly used now and is likely to be deprecated. this button is for evaluating test cases for backwards compatibility with the testrunner. most users will probably not need this button.

read more...

Introduction to Selenium IDE

1)  Introduction to Selenium IDE

2) How to Install Selenium IDE ?
3) How to record and play back selenium IDE ?
4)

read more...

Selenium webdiver

read more...