Quality Testing

Quality is delighting customers

Hi,
These are the questions asked by interviewer, i have given answers but they were not satisfied with my answers, please clarify me on these questions.
1: what are the two scenarios for re-testing?
2:in system testing, which testing types we will use?
3:what are the exact no of test cases u write for username filed using bvp ad equavalence partition
4:what are the differences u observe in web aplication and client server application?
5:why we go for web application (i clearly say web application ,not web testing)
Thanks and advance
Janaki

Views: 498

Reply to This

Replies to This Discussion

Hi Im janaki working as test Engnineer , Im looking for a job in manual testing with 2+yrs exp,if any one have information about openings ,please mail me to janaki.jun07@gmail.com,
Can u please clarify for the questions what i mentioned above,it will very important to me.

Thanks in advance.
Janaki

Sandeep Tripathi (Software Test Engineer)

Mobile No: 9015388433

Email ID: Sandeep.golden@hotmail.com

Current Address: Ushma Urja Apartment Sec 62 Noida

____________________________________________________________

 

Objective

 

To achieve a challenging position in the industry by utilizing my skills, in achieving organization’s goal and thereby enhancing my knowledge and gaining valuable experience.

 

Synopsis

 

2.8 years Full Time Experience Software Test Engineer

 

Technical Skills Details

 

  • ·2.8 years of experience in Software Testing
  • ·Strong knowledge in Software Development Life Cycle and Testing Methodologies.
  • ·Experienced in functional testing, UI, Black Box Testing, System Integration Testing, System testing.
    • ·Experienced in the following Defect Tracking Tools: SharePoint, Microsoft Test Manager
    • ·Having very good experience in HIPPA, HL7 and ICD testing and NIST testing.
    • ·Working on Stage 2 certification

 

Functional:

  • ·Have tested web based application, US healthcare & Healthcare Insurance applications.

  • ·Having good knowledge in healthcare module testing

 

Technical Skills

 

Operating System               WINDOWS 7

Languages                          .Net, SQL,

RDBMS                               SQL Server 8.0 TFS

Application Domain            EHR Practice Management for Healthcare billing, RCM,              

Defect Tracking Tools       Microsoft Test Manager, SharePoint

Soft Skills

 

  • Excellent writing skill including e-Mails, Reports, Chat and good speaking capability
  • Good presentation skill like product/functional demonstration, seminars, trainings to various types of audience
  • Hardworking and congenial in nature having strong value system
  • Highly Studious and Research oriented person with capability of making and keeping the commitments

 

 

 

 

Educational Qualifications

  • MCA from Punjab Technical University

 

Company Profile & Payroll

 

Nexus Development Center Pvt. Ltd.

Job Profile: QA Engineer

 

Project Details EHR Healthcare Application USA                                              from Jun 2011 Current

 

Current Project 1:

Title: Product Testing     Project: EHR                                                                            

 

The project EHR/HIS are web based healthcare application, designed for Physician and healthcare industry, web site name. http://www.nexusemr.com.EHR Application integrates with patient registration, patient history (vitals, allergies, medications, face sheet, immunizations, etc...), billing, document management, messaging, and encounter notes, administration, E-Prescribing and E-Labs into one practice management solution... It has unique model of 5-stages encounter workflow, enrich documentations, and Pay for Performance to several incentive programs, Back-office document services, Clinical Inbox and Health Interoperability Services.

 

Responsibilities:

 

  • Coordinates the development of all approved versions of business and functional specifications for specified applications. Reviews use cases and other technical documents with IT project staff to ensure business requirements are adequately reflected in technical planning documents
  • Fallowed NIST & HIPPA compliance testing, and team member of certification team.
  • Involved in Preparing Test Cases using SRS.
  • Participates in user acceptance testing and testing of new system functionality
  • Involved in GUI, Functional and Regression testing
  • Analyze the Test Results and Reporting the Bugs.
  • Bug filing in bug tracking tool and Involving Full cycle testing.
    • Tests the application as it meets the technical requirements that guided its design and development.
    • Expertise in preparing/review Test Cases, Scripts; execution of Test Cases and Analysis of Reports.
    • Extensive working experience on Functionality/Feature, Performance, GUI, Regression, and Installation Testing.
    • Good knowledge in documentation the module after testing is finished. Expertise in maintaining spreadsheets for overall test strategy.

·         Tests the application where it has defects, flaws, or errors in the application and managed the developers to fix the code bugs.

 

 

 

 

 

 

 

 

 

 

 

Title: Product Testing   Project: EHR Healthcare Insurance Billing       

 

Healthcare Insurance Billing (Revenue Cycle Management): - Revenue cycle comprises of four small projects

Integrated together i.e. Patient Insurance/Eligibility Management and Billing. With Revenue Cycle, organizations can automate four major processes of registration of patients, scheduling of appointments, maintenance of all records and final billing in a synchronized way which reduce paper records, improve work processes and ensure consistency.

 

Responsibilities

 

·         As a Clinical Quality Analyst (Software Tester for Healthcare Applications),

·         Manual test scripts. Supporting Automation and Performance testing.

  • Writing test cases based on the requirements of healthcare payer billing.
  • HL7 & HIPA 5010,1500 CMS testing

 

Extra Activities

 

  • Ongoing case study on all domain
  • Involve in various social activities to spread smiles in society

 

Personal Profile

 

Name                        : Sandeep Tripathi

Date of Birth             : 07/09/1986

Marital Status           : Single

Languages Known   : English, Hindi

Nationality                 : Indian

Other Interests          : Music, Reading, cooking

 

Date:                                                                                                                                                       

Place   :  Noida                                                                                     (Sandeep Tripathi)    

Hi bro,

 

I am having 7+ years expirence in manual testing,

presently working on Mu-2 certification.. if there any openings please send me the profile details to my email id pvarunt13@gmail.com

 

Hi Vicky, I have 3 years of experience in manual testing. if you have openings in your company or if you can give reference . Please let me know. I will forward my profile to your mail id. Please forward details to : msanjeevkumart@gmail.com.

1 --> I could not understand the question.

2 --> Positive testing, Negative testing, Usability testing, etc..

3 --> 3 test cases if there is a input condition like this: "User name must be 6 to 8 characters"

4 --> don't know

5 --> its my right to go for any application.

Positive Testing - testing the system by giving the valid data.

Negative Testing - testing the system by giving the Invalid data.

For Ex, an application contains a textbox and as per the user's Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.

System Testing: It is the process of executing entire system i.e. checking the s/w as well as parts of system.

Testing the application in intranet (without browser) is an example for client -server.(The company firewalls for the server are not open to outside world. Outside people cannot access the application.)So there will be limited number of people using that application.

Testing an application in internet (using browser) is called web testing. The application which is accessible by numerous numbers around the world (World Wide Web.)

So testing web application, apart from the above said two testing’s there are many other testing’s to be done depending on the type of web application we are testing.

If it is a secured application (like banking site- we go for security testing etc.)

If it is an ecommerce testing application we go for Usability etc. Testing’s.

1. Re-testing is the testing for a specific bug after it has been fixed.(one given by your definition).
2. Re-testing can be one which is done for a bug which was raised by QA but could not be found or confirmed by Development and has been rejected. So QA does a re-test to make sure the bug still exists and again assigns it back to them.

3>>>>>

Desktop application runs on personal computers and work stations, so when you test the desktop application you are focusing on a specific environment. You will test complete application broadly in categories like GUI, functionality, Load, and backend i.e DB.

In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This environment is mostly used in Intranet networks. You are aware of number of clients and servers and their locations in the test scenario.

Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load testing.

wHY WEB APPLICATIONS?

Over the past decade or so, the web has been embraced by millions of businesses as an inexpensive channel to communicate and exchange information with prospects and transactions with customers.

In particular, the web provides a way for marketers to get to know the people visiting their sites and start communicating with them. One way of doing this is asking web visitors to subscribe to newsletters, to submit an application form when requesting information on products or provide details to customize their browsing experience when next visiting a particular website.

The web is also an excellent sales channel for a myriad of organizations, large or small: with over 1 billion Internet users today (source: Computer Industry Almanac, 2006), US e-commerce spending accounted for $102.1 billion in 2006 (Source: comScore Networks, 2007).

All this data must be somehow captured, stored, processed and transmitted to be used immediately or at a later date. Web applications, in the form of submit fields, enquiry and login forms, shopping carts, and content management systems, are those website widgets that allow this to happen.

They are, therefore, fundamental to businesses for leveraging their online presence thus creating long-lasting and profitable relationships with prospects and customers.

No wonder web applications have become such a ubiquitous phenomenon. However, due to their highly technical and complex nature, web applications are a widely unknown and a grossly misunderstood fixture in our everyday cyber-life.

1: what are the two scenarios for re-testing?

A -> There are no such thing as 2 scenarios. Re-testing is done to confirm the bug fixes after one cycle of testing is completed. That is you test a piece of software and submit a bug report, the developers fix those bug and then in the next cycle of testing you check only those fixes instead of repeating the complete test and adding more cases to it. It depends of time availability, cost, severity of the issue, complexity of the project and a few more factors which are relevant to the SUT.

2:in system testing, which testing types we will use?

A -> We use all the functional and non-functional testing in System Testing. We test the overall end to end functionality and also the quality characteristics like performance, useability, maintainability, the amount of stress the software can handle, etc.

3:what are the exact no of test cases u write for username filed using bvp ad equavalence partition

A -> When you leave from home for work everyday do you reach office in the exact same time up to the second each day? If not, the same applies to any piece of software/module. Depending on the requirements of the client and the SUT you will have to decide the scenarios and think how/in what different ways you can test it? what can you do to break it?

4:what are the differences u observe in web aplication and client server application?

A web application can also be a client server application and vice-versa. The only difference is if your talking in terms of an application that runs in a web-browser and the one that runs on the desktop. In that case applications that run in web-browser must be tested for cross browser compatibility and both i.e', applications running in web-browser as well as in desktop need to be tested in different OS.

5:why we go for web application (i clearly say web application ,not web testing)

A -> If by web application you mean like websites, then the answer is clear, it is available where ever you are provided you have an internet connection and a device to run it(PC, Laptop, hand held devices, etc).

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2019   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service