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

Post a Comment

Popular posts from this blog

Effective Scrum Meeting

Overview: The Daily Scrum Meeting is held every day through the sprint. At the meeting, the Scrum team gathers to review and synchronize about the project status. In theory, each team member should provide his/her status based on three (03) Q: What did you do yesterday? What do you intend to do today? Is there any issues that blocks your work? # The participants should come prepared: Stop participants that don't come prepared and waste the meeting time. The team members should come prepared to share their updates. You should describe how to answer these questions effectively to increase the synchronization among the team members. The team members should know what is your expectations from them while answering these questions. # Validate that each individual describe the full picture: Validate that each individual can answer the 3 questions (Do not continue until you get the answers or the reasons for why he can't provide them). Validate that each tea...
Post a Comment
Read more

GitHub- how it works

GitHub: GitHub is a platform for hosting and collaborating on projects. We don’t have to worry about losing data on our hard drive or managing a project across multiple computers — sync from anywhere. GitHub Essentials:   Repositories ,   Branches , Commits ,   Issues   and   Pull Requests . A   repository   is the basic unit of GitHub, most commonly a single project.  Repositories can contain folders and files, including images – anything our project needs. Repository = single project = single folder which contains subfolders and files. Sometimes GitHub users shorten this to “repo.” Branching   is the way to work on different parts of a repository at one time. When we are working on a project, we are going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help we manage this workflow. When we create ...
Post a Comment
Read more

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 ...
Post a Comment
Read more