Hot answers tagged

5

Yes, there are situations where you can release to production without testing. Lows Risks: Production systems with users that can miss the systems for a couple of days, might want to recieve features without testing. Small code changes estimated to be very low risk Money risks: Contract deadlines which could kill your company Environment: Having no ...


3

James Bach says "Testing is the process of evaluating a product by learning about it through exploration and experimentation, which includes to some degree: questioning, study, modeling, observation, inference, etc." Some sort of exploration and experimentation can only be done (properly) in production. I see basically two reasons that would demand ...


3

I believe QA should be involved in all aspects of the software design and development process. I believe that if QA is involved early enough in the process, bugs can be avoided rather than merely detected and fixed. In the best situations, I've had my teams participate in all Requirements and Specs reviews. They were trained experts at spotting ...


2

Like continuous deployment, you can you also continuous improvement, with these two crucial steps: Release readiness checklist post-release "lesson learned" meeting. Many of members our our team are former military, air force, marines, navy. And they are used to checklists, and to post-mortem analysis. They say that all these lessons are "written in blood" ...


2

Sounds like you are missing coverage analysis. Whenever we build manual or automated test coverage we should have some way to track the coverage we have created. Historically this could be a simple excel sheet listing test cases by functional area, e.g.: Login_001 - Enter valid sign in and click login button Login_002- Enter invalid sign in and click login ...


2

That feeling is a common one to testers; I don't think you can get away from it. That said, and the terminology is going to differ depend on how you arrange the development process, I'm assuming you have the following things: 1) Some sort of test plan, ie, a list of scenarios you'll attempt, or function test cases you'll run, or whatever. Ideally, these ...


2

It's important to have considered the following testing methods: human testing for issues that automation will miss automated testing for the issues that humans will miss complete run of current test suite on a CI environment smoke testing when the release is live to make sure it works testing on the devices that you know users use but devs (may) not ...


2

What testing types can be used to release the product or project in short span of time. Exploratory testing, you use your common sense to look for bugs. Regression testing, does this new feature break anything that has been working? Crowd testing (not really an official testing technique), you get a few more people to execute exploratory testing using ...


2

In my experience whether or not to test something before release to production is determined by your employer. At my current employer, if something goes into production and isn't right then QA is asked first, did they test it? If they answer yes they're asked, how did it get approved? If they answer no they're asked why not? Also, my employers have let only ...


2

Software quality has a broad scope. Just like Joe says I believe QA should be involved in all aspects of software development. Each person/company just has to find out how much effort and which is appropriate for their situation. Is a good policy? Probably not. As an SQA person that has a lot of dual roles in the past I have learned that a lack of focus ...


1

Is it ever OK not to test something before release to a production? It's totally OK to not test something. As most of the times it's not possible to test everything or to execute all the tests in a given time. So, One of the major tasks of a Test Manager is to prioritize which tests need to be run before release. What a scenario can be, when testing ...


1

Testing is the process of evaluating a product by learning about it through exploration and experimentation, which includes to some degree: questioning, study, modeling, observation, inference, etc. James Bach. Therefore, the level of risk-based testing you will deep depends on the techniques you use to question, study, model... the product and what ...


1

For beta distribution, you can use for example fabric.io (free), and upload binaries with gradle (android) and Fastlane (ios). If you configure fabric in your apps, you have also dashboards with crashes, and much more data. Configuration for gradle (Android): Distribution with Gradle Configuration for fastlane (iOS): Upload a new build to Crashlytics Beta ...


1

If you do not want to rebuild the code make sure the version number is always loaded from a central configuration file. Now you only have to change the file contents, seems pretty easy not? I have a restriction that I cannot rebuild the release once it has been tested, otherwise it all needs to be tested again. This is major bullshit. If the only thing ...


1

Platform Specific For iOS it's the app store. For Android it's Google play - https://play.google.com/store/apps Generally Pre-release you might have: a list of common features that must work on each platform a list of specific features that must work on a given platform schedule of downtime for end users People and Technical resources needed to make the ...


1

Conducting a "bug hunt" or "test jam" is usually a good way to get a lot of testing, and a lot of communication about quality, happening quickly. Conducting a bug hunt means pulling together many people from the organization, developers, PM, marketing, support, managers/executives, and have everyone test the product together. I usually do these for 2 ...


1

I think same tests as for a long span of time, maybe just less of them covering less paths and options. So I still say think about the 4 quadrants of Agile testing and choose which Unit, Integrated, User Acceptance and Exploratory tests to do Still think about the pyramid of testing with (few) manual exploratory tests on top and (many) unit tests on the ...


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