Hot answers tagged

20

It is always a very good practice to start testing as early as possible. By not fully implemented if you mean still under development, then I suppose that is not such a great idea. Yes, you can go for incremental build releases for testing, that might be helpful. When you say that your testers all log the same bugs, well there's your problem! Do you ...


17

I think the problem arrives from how you use your VCS: You want to commit your code because you have finished a sub task and want to have it backed up in case of e.g. a hdd crash on your workstation. Your testers see changes in the repo or get an automated build which they test. One solution could be a separate working branch which is work in progress. No ...


14

To me this is a perfect example of what happens when effectiveness of testers is assessed based on the wrong KPI, in this case, a number of bugs reported. In the end it will harm testers, developers, relationships between tester and developers and as a result product quality. To me this is wrong KPI and there is been at least two discussions here why is so: ...


10

For estimation, the following aspects should be taken into account: Domain knowledge of the team and the requirements. Risks associated with the project. Buffer time. Historical Data. the software life cycle followed by the project. There are a number of techniques which can be used for test estimation, namely: 3-Point Software Testing Estimation ...


9

There will always be bugs that get past a tester and land in production. I have even had bugs that where in my face, we researched it, thought it was a fluke, because we couldn't reproduce it and then released the issue into production. The best thing you can do is learn from it and prevent the same in the future. I write an automated test-case for each ...


8

As Bookeater says, you absolutely want to unify tools and processes between the teams. That said, I'm going to offer some extra advice because I've been in this situation (and to some extent I am still in this situation). Hasten slowly - Each team has built up a process and toolset that works for them. A newcomer telling them they have to change everything ...


8

I do not know what features QC delivers for running automated tests, but this is what I would do to maintain a Selenium test-suite: As a test runner for Selenium just use a unit-test runner in the language you are developing your tests in. Most xUnit-tests runners generate the same result files, which can be parsed by report generators for reporting. To ...


7

For the REST service testing Postman and HttpMaster are good tools. It supports dynamic parameters, validation of response data, various data viewers, etc. If you are looking for performing load testing of the REST services than Grinder and JMeter open source tools can be considered. This data is taken from the post Tools for REST webservice testing


7

Apart from obvious activities like test data creation, test case execution, bug reports...what other initiatives can a QA engineer , take which will help raise his value to the project/Client. You can only do what the situation and context permit you to do. In some shops testers get to review the Requirements before they are finalized. If that's the ...


7

From this and from your other question about using Excel as input for Selenium, I have a feeling that you need to improve your general programming skills. If you are competent programmer, selenium is just yet another library you have to use to make your program to do what you want it to do. Not trivial, but not rocket science either (for a competent ...


6

Most of the companies I've worked for over the last 10 years are using an Agile approach. In this approach there are several factors to pay attention to such as: favor direct communication over formal processes encourage a team approach sit together I find that in such environments you want to seek out practices such as: pairing on test plans before ...


5

First priority should be for everyone to trust the test suite again, failing tests suites will not give this feeling. Disable all the broken tests and run all the tests a hundred times to also get rid of all the flickering tests (that work sometimes, but not always). Start running the tests on each commit or at-least daily to make sure the tests can be ...


5

It makes zero sense to waste time on testing a feature (and reporting bugs, and triaging them) if development is not finished yet. All this work will have to be redone again when code is finished. Something is strange in your process, if testers have so much time that they create extra work for themselves like that, which has no benefits to the project. Do ...


5

Two methods in Scenario Testing System Scenario Use-case and role-based scenarios Test Scenario steps for any application In system scenario, you can use step by step module wise system scenario. In that using module & sub module functionality. example for system scenario Application: Test Scenario 1: Check the Login Functionality Test ...


5

This is a simple, if uncomfortable, situation to be in. Unfortunately, it does happen from time to time and you need to be ready for it. The fact that the defect has been found close to the deadline is, in the short term, irrelevant. Your team has found a high severity defect, so you report it. Given the short timescales, you ensure that everyone who ...


5

Deciding to release with severe bug (and escalate next release with a fix) or postpone release is business decision. QA cannot "assure" quality. QA can "assist" business side with information about quality and process. Business decides what is best allocation of resources: more development, or more testing, or more management and control. In situation like ...


4

I once tested a Windows client UI by randomly banging on the keyboard while my coworker randomly moved and clicked the mouse. I found bugs that way, and I could reproduce them, but (at least initially) I couldn't tell you the exact set of keystrokes and mouse clicks that triggered the problem. That is monkey testing. Exploratory testing is testing ...


4

The question of "Is this application/feature/fix ready for release?" is one that can't be answered accurately, because - as the OP said - there's no way to be sure that there are no bugs in the software. More than that, depending on the situation, the business could have reasons for releasing despite the concerns of QA or testers that the software is not ...


4

I shared this more than once 37 Sources for Test Ideas Become a Skeptic, it will change your view of the product but also of life


4

It depends on the methodology of SDLC we are using, ex: if it is agile development with continuous-integration in place,then it should take 30 percent of development time. Like 15 days development of sprint, then time taken for testing should be 4.5 working days, if key features of applications automated. It also depends number of QA resources involved ...


4

No, it doesn't make sense to test code that you know is incomplete and not ready for testing. But rather than blaming your QA folks... I suggest that you take a closer look at your software development process. It sounds like there is a failure of communication between developers and QA, and a mismatch of expectations. For instance, it sounds like you are ...


4

Is there any general approach or methodology to create complex user scenarios for any application or is it completely context-driven. In the BBST Test Design slides Cem Kaner describes a scenario as "a hypothetical story about the software. A scenario test is a test based on a scenario." He then says a good scenario test has 5 characteristics: The test ...


4

Yes and you're definitely ahead of the crowd already with the plan you've laid out. Additional considerations: In addition to using a Page Object Model, consider a central place for hard coded values (simple methods that return a string in some cases). So the identifiers for the css locator for last_name are in one place (along with other css element ...


4

As you want to test functions that creates random outputs you come across a "fundamental" problem: you can't define an expected output. I write a test, give it an array [0, 1, 2]. I run it 300 times, and check each time is 0 or 1 or 2. But it still have chance that 2 is not appear in this 300 times. So a better way is run it with an "enough times" and ...


4

Seems ok, but you should add also the setup for the framework. how to install the framework what do you need to execute a test/suite (Java installed, selenium, driver if needed) how to run smoke/regression (if you have a lot of tests) additional you could add a small documentation and/or links to online official documentation for: the framework, page ...


3

Testcase format I like one of the following formats: Arrange Act Assert Given When Then These give a clear separation between test phases and steps. How is the test situation setup What is the action under test (try to keep action steps under 10, preferable less) What is verified Details How to write the step details of test-cases greatly depends ...


3

Timebox it and afterwards evaluate. I would say time-box one hour and then see how probable it is the tester will find the steps to reproduce the issue. Often its easier for developers to reproduce the issue, since they understand the code for that part. And they are more proficient in code-debuging.


3

Research and Analyze. Period I think these two tools are enough for a tester to generate creative ideas. And I would like to give you a simple example. Talking of your question, if you would have researched the SQA website well enough, you'd have known that the question put forward by you have been asked multiple times- here and here. If you would have ...


3

Are you recommending the best/most appropriate way to test a problem? Are you thinking of scenarios or perspectives others arn't? Are you making sure you are seen as a valued asset within the team and not just a rubber stamp? What I must stress though, is that there is no "quick fix". The main thing is to build up trust and respect within the team. ...


3

Suggestions: Work on your writing and communication. You've asked two questions in your post, but haven't used question marks. Ellipses have three periods. Learn the difference between its and it's. Use an active voice in your writing. Speak to people more than you email or message. Conversely, don't socialize too much or waste other people's time. Find ...



Only top voted, non community-wiki answers of a minimum length are eligible