Tag Info

New answers tagged

1

As an initial guesstimate I would equal the developers estimation. Obviously you should adjust it to your circumstances, for example do you need to develop automation ? if yes do you have an infrastructure you are familiar with ? is this a new project ? how complex is it compared to previous project you tested ? are there special risk regarding quality like ...


1

This depends on many factors. How accurate and reliable are developer estimates? For throughout the testing needs to be? How efficient you are in testing compared to the developer? How you count time needed for bug fixing and re-testing (and re-fixing and re-re-testing); is it development or testing time? Old rule of thumb is to take original development ...


0

I've found this site to be pretty good: http://www.patshala.com/istqb/ My favourite though is the Skills NB site. You have to search for the course, but the tests are very well done: http://skillsnb-competencesnb.skillport.com/


1

So you would likely be geared more towards an automation lead role and less towards an automation engineer role. While having extreme technical experience is great, you should understand principles more than practice. Development Principles Learn the basics to a few different programming. Buy some development books that focuses more on the principles than ...


4

A few thoughts based on my not-quite-ten years experience as a tester and automator: Learn the principles, not a tool - If you understand the principles of automation and how it works, you're going to be in a much better strategic position than if you simply learn an automation tool. You could do worse than to dig through Joe Strazzere's blog and Alan ...


0

I don't know what SQE is (software quality engineer?) but if you want to get better at white-box approaches then learn to program. Python and Ruby are well known programming languages and both are useful to know if you intend to build automation using Selenium WebDriver. Once you are familiar with programming (or at the same time) start to learn WebDriver. ...


2

You already have a very solid foundation to build on, with your impressive knowledge about QA and your professional skills. If you can supplement that with more technical skills and expertise in test automation, you will have a very valuable (and rare) profile on the job market. From my experience with the many excellent people I have had a chance to work ...


0

Dont forget about www.udemy.com as its a great resource and the teaching is well structured. Now flipping this around a bit, where would you Tod Hostetler start if you had to teach someone on how to become a competent QA Manager as I seem to be getting more and more calls for a Technical QA manager with a development background. Cheers.


0

This is an excellent question. I had multiple times slowed down to ramp up. I would suggest to keep one core strength and develop on others on the fly. Set Learning Goals and Identify Coding Exercises Coding for basic web service, writing unit test code Basics of Java Programming - Datastructures, basic programs exercises Basics of TestNG, Test mobile ...


0

You have really good experience and it would great if you learn automation tool properly. According to me you should learn following tools : 1 - Selenium IDE [Basic selenium using firefox selenium addon to record and verify things] 2 - Selenium Web driver [Using this you can write your own automated script] 3 - Jmeter [It allow you to do best load/stress ...


0

As a start, I would recommend going through this guys blog and working out all of the exercises on his site.


0

I think most people start by looking at the ISO standard.


0

As you already have a pretty nice list of area's where improvements can be found I think the next step is to find the most important thing to improve. I would focus on getting a continuous improvement process going. Possible roads are to introduce recurring retrospectives to identify parts of the process that need improvement.


0

Please identify the Different types of testing that you perform for the application Nature of bugs logged Types Regression Bug Trend How Early does tests find bugs How many priority bugs you find in early cycles What are the tools that QA uses to identify / report issues, Exceptions You need to identify your current state, pain points. Start Fixing ...


0

First of all you need to follow STLC if you want to test any software/Website properly with software testing standards.STLC is same for all. It does not matter what you are testing so STLC is base to start and complete testing with quality. Manual Testing - In most of application there are some areas which really need manual testing. So you need to find out ...


0

Recently my boss tasked me with finding a Test Case manager to hold our regression suites. After extensive research i found TestLodge to be the best in terms of affordability and UI interaction. We were originally using TeStuff but with the comparison in price it was simply to expensive. I was not really a fan of all the web based platforms that i tested but ...


0

A test plan details each step taken to achieve a certain result and states the objective of each action. Follow steps down here: Steps: Write an introduction -An introduction includes a general description and schedule of a test, as well as any related documents Required resources. This section describes all of the resources needed to complete the ...


-1

According to IEEE 829 format : These are the main points : Test Plan Identifier References Introduction Test Items Software Risk Issues Features to be Tested Features not to be Tested Approach Item Pass/Fail Criteria Suspension Criteria and Resumption Requirements Test Deliverables Remaining Test Tasks Environmental Needs Staffing and Training Needs ...


2

Let me give some advice I got from James Bach. He likes to make the distinction between a test plan and the test plan document. A test plan document is the written form of the test plan. This can vary quite a bit depending on the company you work for and in my experience can range from lean or minimal to bloated (I’ve seen so many bloated test plan ...


1

In addition to the other responses: There is always a "specification" in the form of the software itself. Even if there are no user stories or other formal documents, there is a piece of software that does something. From that and the knowledge (however vague) of what the users of the software want it to do - the goal - it's possible to build a test ...


2

I've never heard of "reactive testing" so I'm not sure what exactly that means. Any idea? A blended strategy in the sense of using different test techniques and approaches can be a powerful idea but you (and your fellow testers) need to understand when to use them and when not to. Always make the strategic decision based on the context of your test project ...


0

In my view, this approach can be used only for less formal projects. Normally, test cases are required to exist to verify the functionality and to form a regression pack. This cannot be done without requirement-based strategy. With the suggested blended strategy, testers do not prepare test cases ahead and on most projects, you cannot afford to leave ...


0

That's exactly what we do. Using our own best guest, we evaluate risk of stories coming through the pipeline, test manually what is most important or we get feedback, or test cases as identified in requirements. In "plentiful spare time" we are building a suite of automated regression tests to cover core functionality. It is just common sense. What other ...


0

As answered above there is no such thing as "waterfall testing". Waterfall Model is a software development methodology. There are various other methodologies also. All design technique have their own pros and cons. which methodology to follow, depends on what strategy and processes are followed in ur organization. U can go through the book by Rex Black ...


2

As far as I know, there is no such thing as "waterfall testing". The term "waterfall" is used for one approach to the entire software development lifecycle. See the generic Wiki article here. That being said, test design techniques (and most test-related topics) will remain relevant, regardless of the specific process in your company. I would recommend ...



Top 50 recent answers are included