Tag Info

Hot answers tagged

23

"Value to career" is a tough thing to call. I don't have a certification, and as far as I know, I've never hired anyone with a certification. That could be due to my location, or just a coincidence, or could be a point demonstrating their lack of value. I do know that I've never considered ISTQB/ISEB Certification of any value while reviewing candidates' ...


15

How I think about state models for testing. A state is the system's readiness to respond in a planned way to each of a set of defined events. You know that a system is in a new state (compared to a moment ago) if: The set of events to which it now responds differs from the set a moment ago. The system now responds to given events differently than it ...


9

The difference between statement coverage and block coverage is in the math. Take this example: if (val == true) { DoThis(); DoThat(); DoTheOtherThing(); } else { DoSomethingElse(); } In that example, there are two blocks of code (the true side of the statement and the false side). If the first statement (DoThis();) of the true block executes, ...


9

This is a difficult question, and it really depends on what you want to acheive and what you already have in place. Generating tests can be a long and labourious, and this goes severalfold for automated tests. So the question "how many types of testing should I perform" has the answer "it depends on what you're trying to acheive and how much time/money you ...


7

Abdul, I suspect you are looking for a cookie-cutter approach to satisfy some desired level of confidence. Such a cookie-cutter doesn't exist. Techniques are systematic approaches based on heuristics to help solve very specific types of problems within a given context. "Certifying" a product, or "signing off" from a testing perspecive is either an implicit ...


7

I am aware of the current "certification is evil" line going through the software testing community. I have to say that, I don't agree with this line. As user246 mentioned, people do occaisionally attain this certification to be more marketable. People also often sometimes take this certification early in their careers in the hopes of learning more. ...


6

I wouldn't hire someone based on a QA certification, but I wouldn't hold it against them either. In a tight job market, a person might try a lot of things to make themselves more marketable.


6

"More than the act of testing, the act of designing tests is one of the best bug preventers known. The thinking that must be done to create a useful test can discover and eliminate bugs before they are coded..." - Boris Beizer, Software Testing Techniques 2nd ed. D. Gelperin and B. Hetzel also first suggested the idea of "Test, then code" in 1987. The ...


5

Along the lines of Joe - discuss with others and don't be reluctant to bring in an extra pair of eyes. This helps with "make no assumptions" and is a good de-focusing exercise. No matter how well we try not to make assumptions it is quite easy to slip into them without realizing. Therefore, describing your findings and approach to someone else is very ...


4

Education is an admirable thing, but it is well to remember from time to time that nothing worth knowing can be taught - Oscar Wilde If the effort you make to acquire certifications in the field of software testing in it's current form would encourgae you read more relevant stuff related to testing and you firmly believe that is going to help you think ...


4

If the image is being generated by some process, you should be able to automate just about the entire process right up until generating the image with any data set you want. Rather than testing every single data set being passed into whatever function generates the image, test the image generation the way you would approach testing almost any other unit: ...


4

I would strongly recommend that you consider signing up your team for the Association for Software Testing's excellent BBST series. It's a great introduction to the foundational concepts they'll need to understand why we test, but will also challenge them to improve their skills at explaining and analysing their ideas about testing and expose them to ...


4

There's a lot of ways you can go here - if you want to stay with manual testing you can look to improve your ability to find and report problems, or you can add load testing or functional regression testing to your skill set. Depending on where you're based, the most effective method for you could vary - you'll want to balance between something you enjoy ...


3

Here's another tip: Make your findings public, so that others can pitch in, make suggestions, amplify, or otherwise provide aid


3

I just wrote a deployment validation tool with the ability to validate the following things: IIS Application Pool Exists State (started) Worker Processes Exists State (running) Sites Name State (started) Applications ApplicationPoolName Path PhysicalPath Virtual Directories LogonMethod Path PhysicalPath User Url post/get Validation Response Code ...


3

Well... No, in my opinion the ISTQB Foundation level certification does not guarantee that you can test. Learning the specifics of the job requires practice, depth of knowledge, experience, etc. ISTQB preparation teaches you basic terminology. Processes and even testing techniques are not covered well... Anyway, think about it that way: "ISTQB does not ...


3

State transition testing is perhaps the most commonly used approach in software testing. Everytime a tester performs an action, takes note of the state, then considers the next possible set of actions they are essentially testing transitions between states. Sometimes a state transtion diagram is helpful in simplifying complex systems with multiple states ...


3

State transition diagrams can be a pretty handy communication aid when you're trying to understand how the system is meant to work - it helps you to spot transitions you might miss, if you didn't have the different states drawn out on a whiteboard in front of you. Here's one real-life example. Let's pick an online retailer. We'll look at orders - they're ...


3

State Transition Diagrams are a handy tool in some contexts, but I wouldn't refer to them as a "Software Testing Technique". I don't know what this has to do with a "bog standard clock and light switch".


3

Oh deja vu ... I think that Larry Elison summed it up nicely when he stated that Cloud computing is just, servers and the internet. Video is here -> http://www.youtube.com/watch?v=UOEFXaWHppE Performance testing "Cloud" applications should be tested as though you would test any existing web application. Specifically for performance you would want to ...


3

No, absolutely. The problem with ISTQB Syllabus is that it does not really reflect modern approaches and methodologies (especially in agile environments). I attended ISTQB training recently myself and I must say that at least half of it was useless (problems that were mentioned do not exist in agile team to which I belong). But... Although it does not say ...


3

Does it mean you can test? As has already been stated above several times, certainly not. Does it help? I can't really think of any situations where it would be a negative (at the worst, a non-factor maybe), so it certainly can't affect your employability - which, let's face it, is a rather important part of the "software testing career" experience. On ...


3

Lessons Learned in Software Testing by Cem Kaner et al is a classic source for this kind of wisdom. If you want testing advice from experienced testers, it's a great place to start. You might not agree with everything, but it will get you thinking about how you approach testing in new ways - and that's really the intent of the book.


3

First of all, it is understandable that a former developer might approach testing in terms of individually testable layers or sub-components. However, as a tester, if you do nothing else, you must verify that the finished product behaves correctly when exercised using whatever interfaces the end-user will use. Everything else is secondary to that -- ...


3

Some prevention activities that our QAers provide are Requirements reviews Spec/Design reviews Estimation assessments Providing test data early enough so that it can be used during Unit Testing We'd really like to do more. But in our shop, the schedules and workload dictate otherwise.


3

A thumbnail definition I've used on occasion is "unit tests and good development practice make sure it's built right. QA/Test also tries to make sure we're building the right 'it'" - that is, tester focus tends to be more broad-based and with an eye towards the presumed end user. Some of the resources I'd recommend are active here: Joe Strazzere (All Things ...


2

Judge for yourself: scan the ads and see what % mention certification and what % require it. ISTQB certification shows that you mastered some common body of knowledge and glossary. For me it is a nice-to-have sort of thing.


2

I think the key to your question is "web application". So we should not be directly concerned with which cloud you use or even latency. Performance testing can mean different things to different people. I see it as: Testing speed of pages Load testing You need to know how the application performs in the view of users. Slow pages lower your revenue ...


2

After you deploy to the system, the first things I look for: Deployment specific things? Deployed the right files/folders Ensure that the assemblies that should be signed, in fact, are signed correctly Assembly versions are correct GAC'd assemblies are GAC'd Check desktop icons/start menu icons if necessary (assuming Windows) Check that services are ...


2

We do something similar that we call Release Testing. Basically, we perform just enough testing to confirm that the system has been deployed and configured correctly, that it contains the expected enhancements/fixes, and that it hasn't broken something else along the way. What we actually do during Release Testing varies from project to project, and release ...



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