Tag Info

I know this problem way too well. There's no "right" answer, unfortunately, but there are some things you can do to help with this problem. Dependency map - do you have a list of application features that have heavy dependencies and tend to break when changes occur in other areas? If you know changes in feature X tend to break feature Y, you know you ...

Firstly, I've been exactly where you are and I know the pain you're going through. It's also very 'cool' at the moment for everyone to talk about 'Automation' and how it's a 'golden ticket' to Continuous Integration. Everybody wants their stuff out fast. There are ways to tackle this, but personally, I think a lot of comes with having an understanding of ...

In my opinion, there is incorrect use of terms: User's requirements in plain language should be called user's stories or etc. Requirements for the hardware are often called system requirements. Functional requirements cover what your Application need to do and in which way (i.e. its functions) P.S. Also, you can read about requirements from the wiki: ...

If you want to go fast, you need to assume that once something is tested and working in a cycle, it will continue to work in that cycle. If you cannot make that assumption, you either need to spend more time testing (by yourself or with the help of others) or your developers need to deliver higher-quality code. No one but you and your developers can decide ...

This is the exact problem that bedevils the environment where I work, and have yet to find a strategy that works well and consistently. Some of the strategies and techniques that help are: The testing specialist works with the coding specialists on the unit tests. Even if the testing specialist isn't a coder, knowing the coverage of the unit tests and ...

System requirements are the translations of user requirements in a much more technical language. They are basically the things that a software must perform. Not exactly. The system usually consist of hardware and software. In some situations, it could even include humans performing well defined processes (for instance, changing deployed batteries). ...

Of course it will have unintended side effects - that's what always happens when you crowdsource something, you'll have to expect the same with crowdfunding. The crowd is fickle, you never know what they will come up with, how they will respond, what kinds of natural leaders will emerge - that is a given. But if I had to guess, what will happen is this: ...

I have encountered exactly the same problem and there is no "right" answer, but I can share with you what I've learned: 1) Code changes in one place can cause problems in another. Unless your project is so incredibly well documented that you know exactly what a change can impact, testing the full application on releases is important. 2) Find a balance ...

You have many excellent answers already. Adding my 2 cents to say that your story hits close to home. Management and I have come to an agreeable compromise which is that I created "Mini regression" test scenarios for only the high traffic areas and modules of the program. The Mini Regression is performed as needed, but usually during installation testing. ...

Basically your problem is you are trying to squeeze two months of work into one, make yourself super efficient while also dealing with an inordinate amount of code, and a large group of people who are claiming that you are slowing them down. All true, and while all of the answers given will help, you will also need to use some diplomacy in being able to ...

can you please be precise if you are developing or looking for test suites in Java. Also let us know if you are looking at the unit tests? Apache Commons mail is one very good open source library to send and receive emails. I am sure they must have come up with loads of unit tests for that library. You can download the source code and try out the ...