Today I was in an interview and they asked these questions:
- What test methodologies are applicable for web-based software but not for desktop?
- Can Severity or Priority change during bug life cycle?
To start with, there is no formally defined list of standard test methodologies. That said, there are a number of test methods that are better suited to web applications than desktop applications:
For your second question, yes, absolutely a bug's severity and priority can change during its lifecycle. Some reasons for changes:
I am assuming that the first question you ask is: what are test methodologies for web based and for desktop based applications? because it doesn't make sense when I read it.
Web - relies solely on a browser to test, requires multiple browser testing for valid testing data, need to be mindful of network outages and it's behaviors, etc...
Desktop - relies solely on a users computer to test, requires multiple OS testing for valid testing data, need to be mindful of computer limitations to run the software, etc...
(Those again, are just a few, I could go on with differences for days between these two categories.)
You begin work in a sprint where a 'login' page is being reworked to better suite the customers, this isn't a very high priority because it will be a new page that will replace an existing one that works. During the sprint lifecycle something happens to the existing page that is preventing users from logging in, priority is upgraded on the item by business decision; instead of patching the existing page they would like to roll out the new login page at the end of the sprints work to adequately fix the problem at hand.
Test Methodologies for the web based applications describes about the different types of testing methods, which should be used for ensuring the quality of the product. Testing Methodologies include Unit Testing, Functional Testing, Integration Testing, System Testing and Acceptance Testing etc. These methodologies are part of the Test Plan and one has to define the same before starting the actual testing. Yes, one can always come back and update the test plan for any new method which is required for quality of the product.
Remember Testing Methodologies are very different from Testing Approach, as some people mix both the terms and practices, though both can be part of same Test Plan.
For the second query, yes you can change Severity and Priority of Bug during Bug life cycle, even during Bug Triage meetings Priority and Severity of bugs are discussed and then updated if required. As the name 'Priority' itself suggest 'Importance of Bug' so it is Testing stage dependent.