Tag Info

New answers tagged

1

Niels van Reijmersdal and Dhiman already mentioned the most important point. I'd like to give a look into my experience as my situation was quite similar to yours now some years ago. I'm on a small freetime project (a browser game) and in the past years we tried to build up at a QA too which is a bit more problematic with only users who do the "work" in ...


2

Working with spreadsheets is not bad and strange, it all depends upon the scope and type of tracking you want to do, if you have a limited scope of test cases, issues and requirements, then you can stick to the excel sheets but in long run you will need some tracker which will make your work a lot easier and will itself perform some of your tasks which do in ...


2

One team, one system. Do not create separate spreadsheets, be transparent instead. I would Keep track of your whole project in a single tool. Jira is build to be defect/issue tracker. This is what it was original designed for. Just use it! :) Before development for requirements, during development for defects and communication, after development for ...


0

There are details missing from the question so asking clarification questions would be the first step, the next step should be summarizing your assumptions. Since this is Amazon you should keep in mind while answering some ility words Scalability Parallelism of the test Cross platform (well, this is not a ility word) Traceability, debuggability and ...


0

Latent Bug: The bug that is not identified in the past versions of the software application. which is not fetch or display in past versions of the system. Also refer this Link : https://en.wikipedia.org/wiki/Latent_defect Golden Bug: The bug that is occurred in every instances of the application with severity level high and with high priority. Also refer ...


0

Telling the interviewer what is less important than telling them why. They asked for the two best cases - not just a list of cases. This means that you need to explain to them why these cases are "better" than the many other cases you could have offered up. It doesn't matter if you give good answers if you cannot also explain why they are good answers. A ...


1

This is likely to be geography specific. Where I live, certifications are risky; admitting to having them can actually count against you by suggesting a lack of experience or a narrow view of how software quality work should be performed. Here, in Seattle, WA, I would recommend looking at local community college programs, reading books on software testing, ...


0

Most of my peers (past and present) have ISTQB certs. That is specifically QA. If you want to learn lean, I suggest buying a book on the Toyota Production System as there is no meaningful cert for that.


5

Latent Bug : A latent bug is a bug which is present in the system from previous iterations or release (in your scenario Sprint 1). They are either low priority bugs, which either went undetected or were not reported. Here is a good description : What is a latent bug? Golden Bug : If a bug happens to appear, in every iteration or release, affecting the ...


0

Yes, Agree with above answer, many ways to answering this question, in such I try to define a positive and Negative test cases of the Login page as below: Positive Test Case 1) Verify the Correct username,Correct password - Login Successfully. Negative Test Cases 1) Verify the Incorrect username,incorrect password- Can't Login 2) Verify the ...


0

It depends the size of the company you are looking to work for. If you are going for localization in a multinational organization you may not need to know any of the languages as their are so many they may have linguistic department or may even outsource the work load depending on the volume. If you are looking to work for a smaller company that their ...


2

There are many answers for this question, but first what come's in mind, are: Positive: Data: login: X password: Y User Log in correctly using proprietary data Negative: Data: login: [not registered login] V password: Y User can't log in with unregistered login Data: login: X password: [Bad password] B ...


1

Hebrew is right-aligned and can cause trouble especially when mixed with left-aligned languages. There are a few tips here.


0

For the 'For' and 'While' loop statements, try the Boundary Value Analysis (BVA) and Equivalence partitioning testing approaches. By using these approaches you will be able to create cases for the pending part. http://istqbexamcertification.com/what-is-boundary-value-analysis-in-software-testing/ ...


0

If the value is a floating point or double type then I would suggest the following list of test values: At & Over Limit: 100, 100.0000000000001 (number of zeros depending on the resolution of your float type at 100) & 101 Under Limit: 99.999999999999 (number of nines depending on the resolution of your float type at 100), 99, 0.0 (always worth ...


0

If requirements coverage is your testing goal then any number >100 will do, such as 101. If you wish to be more thorough, then a list of commonly mishandled values such as this one can be a useful starting point.


3

There is difference between Boundary Testing and Equivalence partitioning. With Equivalence, 101 will suffice. For Boundary, you'll need to know (or best guess) the data type. For example, if it is an INT, you can test a value larger than an INT supports. Normally, in this case the number would 'wrap around' to the negative end.


1

Both mentioned products are defect trackers, probably with their own style and workflow. Kanban is a visual process management system, both tools have a Kanban plugin: Mantis: https://github.com/cgaspard/mantiskanban Bugzilla: https://github.com/mozilla/kanbanzilla I would expect both products to deliver similar features with respect to defect tracking ...


1

Coming to this from the safety critical side of the industry I would say that your Risk Management Plan should start with a Corporate level Risk Management Policy that states how you are going to manage the risk aspects of all of your work, for example how risks are categorized, what documentation, testing policies, etc., must be in place and what type of ...


3

I'm going to skip answering the parts of the question that do not make sense or are primarily opinion based. So, which plan should actually contain Risk Management, or it should be completely a separate document? Most software organizations don't do this at all or are not formal about it, so you can probably do whatever you want. If you think it ...


0

Are these metrics relevant for me when I am doing IV&V of a project? The point of IV&V is to have someone look at your project with a fresh pair of eyes and report anything that doesn't match the outlined requirements. This 3rd party wont need anything besides the list of requirements, really. Just think, do they care if your previous tests are ...


1

If you are trying to look for full coverage it seems theirs a gap between automated testing and then the manual type of exploratory testing (Which...maybe I'm wrong, but it feels almost like smoke testing but you don't really have a specific test "plan" for it). Okay, from this description, I think the problem may be that you are limiting your ...


1

ANY test CAN be automated, given enough resources (time and manpower) - but for many tests such effort does not make sense. If user interface or functionality is under constant churn, you are better off do just manual tests, because developing automated test (programs) takes more time, so may not be able to keep up with development (unless you have as many ...


1

I would suggest possibly assigning some "free play" time with a minimum number of participants, specific classes of player or levels of experience and with a number of objectives and/or story points from the core functionality and from the latest couple of sprints to try to achieve within the time period. This could be followed by a structured feedback ...


1

In addition to the above mentioned headers, a test plan should include following sections too along with their description Entry and Exit criteria: for starting the testing phase and calling it out Suspension and Resumption criteria: during testing there may be several instances when you need to suspend your testing because of single or multiple reasons. ...


0

We manage to establish SBO environments & came out with about three different variations. an INDEPT service mild change. a work environment on CRS. And finally a collocation environment were we finally assisted for the development of a refurbished data entry roster of service & assignments,recommendation from institutionalization to occupation All ...


1

Time conversion is much more complicated than you imagine, because different countries/locales switch to daylight saving time at different dates, it is not just one sweep change. And switching back is also not coordinated. http://www.timeanddate.com/time/dst/events.html http://www.timeanddate.com/time/us/arizona-no-dst.html So to convert time between ...


1

It is not "Waterfall testing" , The term "waterfall" is used for one approach to the entire software development lifecycle. The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed fully before ...


2

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: HTML validation - even if a desktop uses HTML display in some or all of its screens, it's not going to be as accessible as right-click - view source in any ...


0

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 ...


1

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. Test methodologies differ greatly between web and desktop applications, that is a wide topic to get into. I can put a few topics on the items listed but there are many good internet ...


0

Although you will be testing on different devices, the test cases should be the same for both operating systems. The test cases should define functionality and expected results given fixed inputs. Although Android and ios are different, I assume you want the application to functionally run the same in both environments.



Top 50 recent answers are included