test execution

Articles

Gauge with a needle in the green zone, showing good performance 7 Simple Tips for Better Performance Engineering

Rigorous practices to reinforce performance and resilience, and testing continuously for these aspects, are great ways to catch a problem before it starts. And as with many aspects of testing, the quality of the performance practice is much more important than the quantity of tests being executed. Here are seven simple tips to drive an efficient performance and resilience engineering practice.

Franck Jabbari's picture Franck Jabbari
Graph showing how testing earlier costs less and means fewer overall defects The Shift-Left Approach to Software Testing

The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization.

Arthur Hicken's picture Arthur Hicken
Dial with the needle moving from red to green A Better Way of Reporting Performance Test Results

Reporting the results of functional tests is relatively simple because these tests have a clear pass or fail outcome. Reporting the results of performance testing is much more nuanced, and there are many ways of displaying these values—but Michael Stahl felt none of these ways was particularly effective. He proposes a reporting method that makes performance test results easy to read at a glance.

Michael Stahl's picture Michael Stahl
Are functions in page objects for big projects a good practice?

So, I'm writing automation tests for a huge web platform. We have page objects folder with files for each web page which contain a great amount of selectors used in tests. Also, tests pertaining to one of the component/functionality are all grouped in one file. 

 

The main question is whether the functions used by multiple tests (and some will have assertions in them) should be written:

1. Functions w/o assertions in page object and those w/ assertions in helper file for that component/functionality

2. All functions in helper file

3. Functions w/o assertions in page object and write the rest of the commands with assertions in the specific tests even though they may repeat and make the file with tests huge.

Testing is done in javasctipt(more recent: typescript), selenium webdriver, protractor, jasmine.

I really hope someone can solve this conundrum since nobody in my office has enough experience to help me. Thank you!

Z R's picture Z R
Graph showing boundary values Using Equivalence Partitioning and Boundary Value Analysis in Black Box Testing

Equivalence partitioning and boundary value analysis are two specification-based techniques that are useful in black box testing. This article defines each of these techniques and describes, with examples, how you can use them together to create better test cases. You can save time and reduce the number of test cases required to effectively test inputs, outputs, and values.

Josh Giller's picture Josh Giller
What are the future options for one year experienced software tester?

What are the future options for one year experienced software tester?

Prasanna kumar M T's picture Prasanna kumar M T
Experience or knowledge of performing acceptance testing on automated conveyor systems

Does anyone here have any experience or knowledge of performing acceptance testing on automated conveyor systems utilised for the sortation of items.

This is a mixture of software and interfaces with moving machinery and integrating into data systems 

For example conveyor or materials handling conveyors used in the managment and distribution of luggage around a large airport 

I am looking to understand how you defined the scope of test and the framework adopted with the possibility of benchmarking the activities you have performed.

Any advice would be greatly appreciated.

lee marshall's picture lee marshall
Racecar on a track Test Faster: How We Cut Our Test Cycle Time in Half

In just a year, one test team reduced its test cycle by more than 50 percent. It took analysis, planning, and effort—first they looked into how they spent their time, and then they questioned whether they could reduce time in any of those areas. Once they knew where they could be more efficient, they could start tackling their blockers. Here's how you can, too.

John Ruberto's picture John Ruberto
How to test mPOS applications. Is anyone aware of any tools to test mPOS applications?

mPOS applications are Mobile Point of Sale Applications. How to automate the test cases for such applications

Rasika Dravid's picture Rasika Dravid
Person using a mobile app on their phone, photo by Erik Lucatero Evolve Your Mobile Usability Testing Methods

Today’s mobile behaviors and expectations have radically changed, a result of the continuous evolution of mobile technology and the myriad new ways users can now interact with mobile. Because of this advancement in technology and user behavior, testing organizations must also advance their mobile testing solutions to ensure they continue to deliver the most intuitive, up-to-date experience possible.

James Hoshor's picture James Hoshor

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.