Back To Normal

Subscribe To Our E-Mail Newsletter

Showing posts with label Manual testing. Show all posts
Showing posts with label Manual testing. Show all posts

Sunday, July 2, 2017

View of Quality

Generally quality stands for “standard of product measured against the other things of similar kind” and software person measure the quality in degree that a product is reliable ,maintainable and sustainable.
 When you view the quality from different stakeholder perspective
  • Users will observe the external factors (speed and usability) of the application.
  • A business Stakeholders measure based on the financial performance
  • Developers care about the internal code structure of the application
  • Testers trying to connect all the dots.

   
Quality pyramid with Moslows hierarchy



                                                
Satisfying needs on lower levels bring demising returns. And our quality of life improves by satisfying  high level need after lower level needs are satisfied.

How can I relate the Maslow hierarchy with software quality?


  •  What are the key features and key technical qualities?
  • What are Key performance , security, scalability aspects?
  • Usability scenarios (Is it usable?).
  • What production metrics will show that is used in real work?
  • Is it successful?  what business metrics will show that this was worth doing? is it operating within financial constraints
Read More


Saturday, December 6, 2014

Test Coverage

Test Coverage Symphony :
           In my three years of experience in symphony , we have tracked automation coverage by comparing automated test cases against manual test cases. Whenever my manager asks the report, features based automated test count shared with him. The manager always informs us, Test coverage should be more than 80% percentage.
    To achieve 80%, we have worked , since two to three years and automated nearly 10,000 test cases, which runs for four days  in five to six VMS.

In over all, test coverage is not worked out to certify the quality of application. It never going to helpful to achieve bug free application, and still customer facing problem of production defects.

Test Coverage Huawei :
         Huawei is process oriented company and they will follow customized agile (scrum & XP) .Huawei needs all kinds of test reports(Test Plan, Test cases, Test summary, RCA, Retrospective) to certify quality. All these test reports are maintained based on the iteration and release.

Test coverage perspective , we need to keep track of Integration tests should be more than 90%, and functional Test  should not be less than 80%. Agile coach will audit all teams and give rating based on process and document. If functional & Integration tests are less than 80%, then coach will declare that team as low performing.

           Its mostly forcing us to maintain all reports , irrespective of quality of application. In over all , they will measure quality of application based on process and test reports. I can see , still Huawei is struggling to get customer satisfaction ,to ensure the quality.

Test coverage in Thought-works.
       Thoughtworks is agile oriented company and they will never believe on test reports. They will always choose , TDD or BDD type of development.
First write your test and write your code to pass the test, it will push all tests into lower level and keep minimal number of tests in higher level.
       This way of working is totally new to me , they never write any manual test cases . There is no way of tracking test execution results , developer will automate all possible scenarios in Unit level and Integration level.
     
       Responsibility of Tester , he will review all tests with respective to story and if there is any uncovered scenarios, then he will add into respective levels.  With respective to test coverage , they will track Integration and unit Test coverage , but never compare automated test cases into manual tests case.
      If clients are asking any kind of test reports , then they will prepare minimal report or either convince client and explain test approaches to client.

  If you have time , please read this post ,

   



Read More


Tuesday, December 2, 2014

Bug free Application

A lot of time I had asked the same questions to me, I couldn’t find the right answers.  I have collected metrics from my current projects ,what they are thinking in terms of bug free software application.

 Since we had done two RCA on production defects in the current year  and listed the outcomes.
There is no check in micro service for negative stock.
Missed scenario during development and testing
Boundaries are not Tested based on cost status (S, G)
Data pull job is not tested 
Not tested against real data especially for dc discount
Don't have functional and unit test for events.

 There are best practices one can engage to reduce the probability of bugs from appearing.

      In real world , Is there any application with 100% bug free? No, its impossible to certify 100% bug free application but we can deliver workable software to customers. How does google ensure quality of application to end-users? 

  
From My experience :
If we meet the following expectation of customer ,then we are delivering the bug free application 
       The client should be happy with delivery,and it should meet their expectation.
       End users should not have difficulty to use the application.
       Enough help or guide should be provided to end users.
       They should not ask , any queries to understand the functionality.
       



Read More


Wednesday, September 26, 2012

Top Five Testing Blogs

I have found top five testing blogs for software testing . This blogs are really useful for software tester who want to know or practice new concepts .

James Bach  : http://www.satisfice.com/blog/

Agile : http://agiletesting.blogspot.in/

Martin Fowler : http://martinfowler.com/

Tester Tested : http://testertested.blogspot.in/

Test This blog : http://www.testthisblog.com/

Some useful Top 100 list will be listed in below urls.

http://www.testingminded.com/2010/04/top-100-software-testing-blogs.html

Read More


Thursday, June 3, 2010

Define Priority and Severity?

severity defines the importance of defect with respective to functional point of view..

priority defines the importance of defect with respective to customer point of view
Read More


Wednesday, March 3, 2010

How do we represent the bussiness logic ?

Bussiness logic may be represented by following ways
  • Flow Chart
  • Decision table
  • State machine
  • Use case
Read More


how do we combine the various test values for each test data element?

1. Exhaustive
2.one data at time
3.Deductive / analytical
4.orthogonal arrays.
Read More


Types of test data design techniques?

1. Boundary Value analysis
     Test the planned limits of the software. Test the valid ,last possible and invalid data just outside the boundary.
    Boundary types;
  • numeric
  • Character
  • Position
  • Quantity
  • Speed
  • location
2. Equivalence partitioning

     An equivalence class or partition is a set of test cases that test the same thing or revals the same bug.

3. special value

     select the test data on the basis of features of a function tester use the domain knowledge or prior experience or error guessing.

4. Error based

Generate the test cases based on
  • programmer histories
  • programmer complexity
  • knowledge of error prone syntactic construct
Guess error based on data type

5. Input/output domain.
  • Looking from input sides , generate inputs to map to outputs
  • also ensure that you look from output side to ensure that you have generated all possible inputs.
Read More


Types of Test Design techniques?

1.use specification
2.use structure of code
3.Use past historical data
4.learn from each test execution cycle( domain knowledge)
Read More


Define Test Scenario:

Test scenario is a thread of operational use at any level of testing.
  1. At system level , the operational use is one such use/abuse by the end customer
  2. Scenarios are long at system level and short at unit test level.
Example ;Login screen

TS1 : Ensure that an invalid user is disallowed tobe logged in
  1. tc1: invalid name - Name is null
  2. tc2: name is too long
  3. tc3: name contains illegal character
  4. tc4: name is not a registered user name.
Read More


Define Testcase:

Testcase may be defined as an input-output pair with an expected result.
Read More


Friday, November 27, 2009

What is the use of plan in Automation?

 The purpose of the software test plan is to prescribe the scope, approach, resource, and schedule of the testing activities
         The following are the important topics, which helps in preparation of Test plan.
             1.High-Level Expectations
             2.People, Places and Things
             3.Inter-Group Responsibilities
             4.Test phases
             5. Testing strategy
             6.Bug Reporting
             7.Metrics and Statistics
             8.Risk analysis.

Test Planning:

    Test plan: The Test Plan describes the tasks, schedules, approach, resources, and tools for integrating and testing the software application
    The Test Plan answers such questions as:
  •      What is being tested? 
  •      What are pass/fail criteria?
  •      When will each test occur?
  •      What hardware and software environment is required?
  •      What features must be tested?
  •      What features will not be tested?
  •      What are the responsibilities of individuals and organizations involved in the project?
     Identify the various modules and decide which modules/functionalities will be tested. Clearly mention which items are out-of-scope for testing
     List down the priority of testable items (conflict-resolution between the various players is of importance)

The test plan should include:
  •     Scope of the application being tested
  •     Approach to be taken (in detail)
  •     A tentative go live date
  •     A list of functions and procedures to be tested and their priority
  •     A list of who is responsible for testing each function and procedure
  •     Various milestones and timelines
  •     Details of the resources
  •     List of all deliverables
  •     Risk and mitigation
  •     Specifies roles/responsibilities of the various players: business analysts, technical analysts, development team, testing team, etc
Read More


What is Regression testing?

 Regression tests confirm that implementation of changes have not adversely affected other functions.  Regression testing is a type of test as opposed to a phase in testing.  Regression tests apply at all phases whenever a change is made.
Read More


What is system Testing?

 The system test phase begins once modules are integrated enough to perform tests in a whole system environment.  System testing can occur in parallel with integration test, especially with the top-down method.


Types of System Testing:  Refer the below URL

 http://en.wikipedia.org/wiki/System_testing
Read More


What is Integartion testing?

Individual components are combined with the other components , validate the communications,data sharing and links occurs the properly.
Integration testing : Divide into the following  three approaches
  • all-at-once
  • bottom-up       
  •  Top-down           
     Bottom up: Integration testing start from the low level components and end with the high level components.
     Top down: Testing will start from the lop Integrated level modules and connect to the branch level modules.
     all-at -once : it will Combine both top level and botton level members.
Read More


560 Free Online Courses

Top 200 universities launched 500 free online courses.  Please find the list here .