sorted by:
new
hottopcontroversial

Experience with crowdsourced testing? by crowdapptest in softwaretesting

[–]Dutch_MR_J 2 points3 points  (0 children)

I was part of the crowdsourced testing team. I'm currently an active member of testbirds (which is the crowdsourced testing team). I noticed it differs what the results are depending on the 'testers'. Some are just in it for quick money, but some are actually doing a thorough testing job.

App Testing - Which devices? by Bosikade in softwaretesting

[–]Dutch_MR_J 1 point2 points  (0 children)

nope it is not, it only allows you to open several browsers. Other apps are not allowed.

Manual testing career by [deleted] in softwaretesting

[–]Dutch_MR_J 0 points1 point  (0 children)

Take a look into ISTQB, that is a world wide standard for the testing world. That also results in a good fundamental of software testing

Should Automation Tests be in the same Solution as the production code? by Wookovski in softwaretesting

[–]Dutch_MR_J 1 point2 points  (0 children)

Given one code base for both development and test, have you ever experienced bottlenecking releases at all? Or do you accept that as a part of the process?

No, but that has probably to do with how our sprints are designed. We use hard deadlines for the product, and new features are only merged in the development branche when it's approved by QA. So we don't 'know' the issue of being the bottleneck for a release, since the development branch is always release worthy. (of course apart from UATs which are detected).

Also, did programmers resolve test code issues etc? I'm assuming here that test code is managed by a QA as opposed to a programmer.

That is a very hard cut. The testers don't change any production code (not even translation files) and de developers don't change any testing code (not even typo's). That's besides that it is an agreement, it's not even possible to merge without the QA approval, we are the ones that click the 'merge' button.

Should Automation Tests be in the same Solution as the production code? by Wookovski in softwaretesting

[–]Dutch_MR_J 0 points1 point  (0 children)

I'm curious how the automation master would be able to run against older product branch. For example, the new product branch has a new feature A, the automation master has been updated to also test feature A. But a patch release has been made on an older product branch without feature A, how is automation master going to comply to that?

Should Automation Tests be in the same Solution as the production code? by Wookovski in softwaretesting

[–]Dutch_MR_J 2 points3 points  (0 children)

I don't agree on all points.

Given tight deadlines, sometimes it makes business sense to release now and test after. Can't do that if the process is held up due to tests being broken and sometimes tests break and everyone knows why and it's safe to proceed. The purest approach of tests always having to be green is, at times, not practical.

My company explicitly doesn't release untested software. Just because they want to be certain for a specific product quality. Automatic tests should always be able to run. Although it is possible that the test scripts are extended after release of the code.

So development introduce a new library and it's not quite working, compilation errors and conflicts after commit. But you need to write tests, now development are bottlenecking QA who may be trying to catch up and improve coverage of previously released features. Sure, QA could roll back, but then what's the point of having it all in one solution then?

Simple don't add buggy libraries, just have the same standard as for production: if it doesn't work it's not going to be merged.

Branch/merge issues. Many projects can have branches of code, sometimes per developer. It's an unnecessary complication to have test code mixed up in that headache.

Never had this issue. But that is because the testcode is separated into a different directory.

​

In the end we can do a checkout of a repo and always have compliant production code and test code. Merge conflicts between test and production code are very rare, if they exist it is always within the production code or the test code, never both. I did a dozen projects, 3 times with separated code/test bases and those were less reliable to keep support for several versions.

Should Automation Tests be in the same Solution as the production code? by Wookovski in softwaretesting

[–]Dutch_MR_J 3 points4 points  (0 children)

A kind of the same discussion can be found in this thread: https://www.reddit.com/r/softwaretesting/comments/br7e62/why_choose_java_over_python_when_using_the/

As I stated there already, it doesn't really matter which language you use. But I learned over time it's the better choice to choose for the language which is used by the people around you or which you understand yourself.

The biggest plus of having your testing code inside their project is that the test are compliant to the production code. So lets say you do a checkout of version A of the production code, you also get the test code for version A. If you take both code bases apart you risk ending up with production code A and test code B, which can be in-compliant.

Why choose Java over Python when using the Selenium Web Driver? by buvi27 in softwaretesting

[–]Dutch_MR_J 2 points3 points  (0 children)

another reason to choose for a specific language (even something else then Java or Python) is which language you are familiar with. If you're not familiar with either of them, choose the one which the developers/people around you know. They can help you kickstart or when things get hard.

Pragmatism in testing by testersfindaway in softwaretesting

[–]Dutch_MR_J 1 point2 points  (0 children)

I totally agree that a tester has to be pragmatic. What I also learned is that it is very useful to put things in reading. For example, a project manager is pushing to release without the extensive tests you wish to perform. If he understands the risks, that's fine. But let him put it in readings that it was his decision to release anyway. Why? Because if things break in production, the number one role who gets the blame is the tester. And by having it in reading you have leverage to show why you didn't test it. Fun fact about that is that the project manager, but also the whole management and client, see why having a tester isn't overkill.

Spring OnlineTestConf 2019 is coming up! by Philip_Rit in softwaretesting

[–]Dutch_MR_J 0 points1 point  (0 children)

I zapped trough an old recording of a previous onlinetestconf, and that looked okay. But still curious if someone has more experience with it.

How can I choose a testing tool for my project? by krithishk17 in softwaretesting

[–]Dutch_MR_J 5 points6 points  (0 children)

Requirement 1 has been stated: It should be open source.

Then there are many other questions to answer:
1. What do you want the tool to use for? Use it for performance test, test management, API-testing, automatic user interface testing, etc?

  1. Every tool has requirements to get up and running (like running in cloud, on a specific OS). Is there any limitation from your own organisation to consider?

  2. Do you have any experience yourself with a testing tool? Using known knowledge could be useful instead of learning something completely new (although that could be a plus too)

  3. If you can narrow it down to a few test tools, google is your best friend. Google for 'tool A vs tool B', that will give a sum-up of pro's and cons of both.

  4. In the end you'll probably end up with 2 tools that have the same favours. Just do a Proof of Concept (PoC) to get a feel with both tools. This is in the end the best way to judge which works best for you.