Skip to main content

Important Questions



Important Questions related to QA


  1.  What is the difference between Bug and Defect?

    Answer:

    A bug is the result of a coding error
    A defect is a deviation from the requirements

    That is: A defect does not necessarily mean there is a bug in the code, it could be a function that was not implemented but defined in the requirements of the software.
    https://en.wikipedia.org/wiki/Software_testing.
  2.  What is Validation and Verification in terms of Software Development?
  3.  Flow-chart of the Facebook login page. Plus, test cases to cover the scenarios.
  4. List of CASE tools.
  5. Boundary-value analysis.


  6. Python:
    1. is Python OOP?

    2. if not, how Python implement the behaviour of OOP? Answer: using 'self'.

    3. use of Self in python.

    4. Priority and severity: Example of bugs with high/low priority as well as low/high severity.
    Example:
    a. Typo in About us page.
    b. Financial application: interest should be 5%. But the issue is now it's 10% in code.
    The impact month is then next January. The issue is found in June.
    So we have time to fix and the client won't impacted.

    5. Max and Min value text fields. Salary range= 50k-80k.
    What should be the values in the text fields to test the search result? How many combinations or steps?

    6. Explain flows in design and functionality of the Login page as QAE.
    Answer: Suggestion about the logo, Remember me, sign up, for example.

    7. SDLC, STLC, BUG LIFE CYCLE- Steps.

    8. page object model, unittest, pytest.

    9. Convention of implementing methods as Test Method in Python.

    10. Search logic in web application testing.

    11. Web application and desktop application: what needs to and need not to test. Answer:
    In a web application, we need to test security, stress, performance, connectivity.
    In a desktop application, we don't need to test above. One user per application.

    12. Elements or components of a Test plan, Test case.
    https://reqtest.com/testing-blog/how-to-write-a-test-plan-2/

    Test Plan:
    It describes the scope of testing, testing techniques to be used, resources required for testing and the schedule of intended test activities. The scope helps in identifying test items and the features to be tested. A test plan also contain details of who will perform a given task.

     Postman
    a. what would be tested for any API.
    b. how to write tests on Postman.
    13. 


Comments

Popular posts from this blog

Verification and Validation (V&V)- a software testing approach

Verification: It focuses on PROCESS related activities to ensure that the Products and deliverables meet a specific requirement before the final testing. Can be done through: A. Technical review B. Business review C. Management review Simply: Are we building the product in the right way?  that is, does the software conform to its specification verification  is the process of checking that the software meets the specification. Verification is an example of QA Validation: It focuses on PRODUCT related activities, that attempt to determine if the system or project deliverables meet the customer or client's expectations. Will be done by: Testing. Simply: Did we build the right product?  that is, is the software doing what the user really requires. Validation  is the process of checking whether the specification captures the customer's needs. According to the Capability Maturity Model(CMMI-SW v1.1) we can also define validation as The process ...

Smoke Testing vs Sanity Testing

Differences between Smoke Testing and Sanity Testing are as follows: Topic Smoke Testing Sanity Testing Purpose To verify the BASIC or CRITICAL existing functionality of an Application- before starting rigorous testing. To verify NEWLY ADDED/UPDATED functionality or BUG FIXES. Who does these testing? Performed by both TESTERS and DEVELOPERS Performed only by TESTERS Can these tests be automated? Can be automated Can’t be automated In technical terms Exercises the ENTIRE system from END-TO-END Exercises only a particular COMPONENT of the entire system In general terms SHALLOW and WIDE range of testing. More like a GENERAL HEALTH CHECKUP Narrow and DEEP approach of testing. More like a SPECIALIZED HEALTH CHECKUP

Quality Assurance vs. Quality Control

            Quality Assurance             Quality Control Definition:    QA is a set of activities for ensuring quality in the processes by which products are developed. QC is a set of activities for ensuring quality in products. The activities focus on identifying defects in the actual products produced. Focus on:    QA aims to prevent defects with a focus on the process used to make the product. It is a proactive quality process. QC aims to identify (and correct) defects in the finished product. Quality control, therefore, is a reactive process. Goal:   The goal of QA is to improve development and test processes so that defects do not arise when the product is being developed. The goal of QC is to identify defects after a product is developed and before it's released. How:   Establish a good quality management system and the assessment of its adequacy. Periodic conforman...