New answers tagged

0

We actually have a great solution for this case in PractiTest: 1. Create a test case with the sequence of steps that are going to be repeated; 2. Now you can use this sequence in any other test cases: for example, if you need to enter this sequence after the step “Switch from Payment Method 1 to Payment Method 2”, you just use “Call Steps from another Test” ...


0

As for format, again, it really comes down to what is most helpful for you and your consumers That is true! For us we had some struggle with our customers. Because the customer was complaining that testing was not "visible" within the department. Hence we decided also to add exporatory testing but with Kanban Board (at the same time it was also our bug ...


0

As per my experience in the qa services, the practice 'Repeat steps 1 to X' can be followed while creating test-cases with repetitive steps. The only thing we need to make sure is to provide the test-credentials separately for each test method. The other approach that can be followed, is to segregate those common steps in one section and that section can be ...


1

Developers have the same issue when using open-sources libraries in the application you are building. Most developers also do not have the knowledge of most security risks this brings into their application. This is a serious issue, this article gives some real world examples where security was breached in open-source libraries: How Hackers Infiltrate ...


3

Adding to @Alexey R. answer. You should definitely rely on the community for evaluating and finding security and other issues. The same applies not only for test frameworks but also for tools and packages used in your product in production. But that doesn't make you immediately resilient to problems, scroll through NPM's advisories and you'll see critical ...


4

I'm afraid the general answer would be "you have to rely on the community" since the code is visible to huge amount of people, a lot of people review it and anyone is free to publish their concerns about the safety of any particular piece of code. This gives quite a strong belief of there is no backdoors added intentionally. This of course does not protect ...


0

The way the industry is trending, it is a good idea to learn how to code. With all of the different languages, tools, and free resources available, there is no better time than now. You don't need to become a master coder, you just need to learn how to write automated tests, which should lighten your workload. The ability to adapt to change is a ...


Top 50 recent answers are included