Highlight

In the high-risk world of space exploration, precision is everything. A single misplaced decimal place, an omitted character or a small syntax error can mean the difference between success and catastrophic failure. One of the most infamous coding errors in history - the absence of a hyphen - led to the destruction of NASA's Mariner 1 spacecraft just moments after launch, costing the agency a staggering 18.5 million dollars. On July 22, 1962, NASA's Mariner 1 was ready to embark on a groundbreaking mission to the planet Venus. The spacecraft was designed to transmit valuable scientific data back to Earth, advancing humanity's understanding of the solar system, yet just 293 seconds after liftoff, the mission ended in disaster: The rocket veered off course, prompting ground control to initiate the self-destruct sequence. The culprit? A single missing hyphen in the guidance software code. The missing hyphen led to incorrect speed calculations, causing erratic flight behavior that eventually made the spacecraft uncontrollable. In short, the Mariner 1 spacecraft relied on a combination of ground-based and on-board guidance systems, and its software was responsible for interpreting the signals from the tracking stations and adjusting the rocket's trajectory accordingly. The missing hyphen in the code disrupted the mathematical instructions that dictated the velocity corrections, resulting in erroneous calculations. The error translated into unintentional trajectory deviations that became increasingly serious, leaving NASA with no option but to abort the mission. This incident remains one of the most costly typographical errors in history, highlighting the critical importance of meticulous attention to detail in programming, particularly in mission-critical applications. In the world of software development, even the smallest oversight can have far-reaching consequences. This is especially true in aerospace engineering, where precision is paramount. For today's developers and engineers, the failure of Mariner 1 serves as a cautionary tale; it underlines the need for rigorous code reviews, extensive testing and redundancy in mission-critical systems. Today, software verification processes, automated error detection and simulation-based testing have evolved to reduce these risks, but the lesson remains relevant: every character in the code matters. Although the Mariner 1 incident is among the most famous coding errors, history is littered with other examples of small mistakes that led to catastrophic results: Explosion of the Ariane 5 rocket (1996): A software error in the inertial reference system led to the self-destruction of this European Space Agency rocket, causing 370 million dollars in damage. The Mars Climate Orbiter (1999): A failure to convert units from the imperial system to the metric system led to the spacecraft entering Mars' atmosphere at the wrong altitude, resulting in mission failure. The collapse of AT&T's network in 1982: A single line of faulty code in a software update caused a massive telecommunications failure, affecting 75 million phone calls. The Mariner 1 disaster underlines an essential principle in both software engineering and wider technological endeavors: the devil is in the details. Regardless of how far technology has advanced, the fundamental need for precision and complete validation remains unchanged. In today's fast-paced digital world, where software governs sectors ranging from finance to healthcare, ensuring accuracy at every level is more important than ever. The original article via YourStory can be read here. 

Opinion article by Giridhar Rajkumar. 1. Integration of AI and Machine Learning The role of AI and machine learning in the software testing industry continues to grow every year and is predicted to become increasingly influential. AI will transform various software testing activities, including generating new test cases, enabling self-healing capabilities and creating test data to reduce manual effort. It improves automated testing by creating code snippets, thus allowing testers to focus on their core tasks. In addition, AI supports testers by prioritizing critical tests, detecting anomalies and identifying the root causes of system failures, or of the tests themselves. This includes categorizing failures into product defects, automation defects or faults. 2. Shift-Left and Shift-Right Testing In today's fast-paced software development lifecycle, it is essential to get feedback on tests quickly and efficiently. Traditional software testing methods can delay the development lifecycle by providing information in later phases: Shift-Left testing is an approach to getting feedback faster to help programmers fix problems/defects as quickly as possible, helping to reduce the cost and time associated with fixing defects. On the other hand, they can also be improved by Shift-Right testing, which extends testing into production, using techniques such as A/B testing, canary releases and blue/green deployments to gather feedback from users. Active monitoring systems gather information on performance and identify faults to ensure that the software meets real-world requirements. Once a feature has been released, end-to-end testing, which includes user interface testing, can also successfully validate it. 3. ethical AI testing AI is playing an increasingly important role in software testing, but ethical practices should guide its use. As AI evolves, it can unintentionally generate biased results, leading to unfair or discriminatory outcomes. And that's where ethical AI comes in. Ethical AI testing ensures that systems meet key standards such as fairness, accountability and compliance with regulations such as the GDPR (General Data Protection Regulation), which protects sensitive data. This means continually testing the results produced by AI systems to maintain security, robustness and reliability. 4. Increasing Demand for Low-Code Testing Platforms The demand for low-code testing platforms continues to grow as many organizations prefer faster and more efficient ways of delivering high-quality software. These platforms allow non-technical stakeholders, such as commercial and UAT (user acceptance testing) testers, to create, execute and maintain automated tests with minimal coding experience. By bridging the skills gap, low-code platforms promote seamless collaboration between the company, developers and testers. Simple drag-and-drop functionality speeds up test creation, reducing test development time. With CI/CD support, low-code platforms allow tests to be run efficiently from pipelines, providing quick feedback. They help simplify Agile and DevOps practices, increasing their accuracy. In addition, low-code tools increase scalability, simplify maintenance and increase productivity by automating repetitive tasks, making software testing more reliable. 5. cybersecurity-focused testing By 2025, cybersecurity testing will increase among organizations as the frequency of cyberattacks increases. Many reputable organizations are increasingly vulnerable to threats such as phishing, data breaches, distributed denial of service (DDoS) attacks and ransomware, which can lead to financial losses and operational disruptions. Companies therefore need to consider implementing cybersecurity into their development lifecycles. One such approach is DevSecOps, in which security is applied at every stage of development activities. Proactive practices such as penetration testing, static application security testing (SAST), dynamic application security testing (DAST) and threat modeling can help organizations identify vulnerabilities early and mitigate risks proactively. AI-based tools can help with real-time monitoring, faster attack detection and predictive analysis to stay ahead of evolving threats. The continuation of the original article via Get XRay can be read here. 

Opinion article by Brooke Masters. With the spread of electric vehicles and more sophisticated systems, managing updates will only become more important as they become more popular, and the digital information and safety systems of gasoline vehicles become increasingly sophisticated. Software patches accounted for 15% of vehicle recalls in the US last year, compared to 6% five years ago, according to data from the National Highway Traffic Safety Administration. Last year, BMW was the target of three software recalls in the US, more than many of its rivals, according to the same organization's records. Globally, Ford registered the highest number of cases, with 19, closely followed by Chrysler. Tesla had the largest market share, with 50% of the 16 recalls requiring software fixes. This is not surprising, given that electric cars rely much more on software and have fewer parts than internal combustion engines. But the recall data only scratches the surface of a wider software problem: Like cell phone providers, car manufacturers regularly use updates to improve existing features and sell new services to existing customers. Most manufacturers send out updates on a regular basis, covering everything from interior lighting modes and battery usage improvements to important safety changes. "It used to be that you could manufacture a car, wrap it up and sell it," said Kevin Mixer, senior analyst at consultancy Gartner. "The automobile is now a living platform... Companies are learning in real time." This is proving more difficult for traditional car manufacturers than for emerging competitors. Last year, when Gartner ranked car manufacturers according to their digital performance, the top seven were all Chinese and US electric vehicle manufacturers, including Rivian, Tesla and Nio, while traditional manufacturers got a dismal average score of 33 out of 100. Software problems have delayed recent launches at companies such as Volvo and General Motors. Frustrated with in-house software development, Volkswagen executives signed a 5 billion dollar partnership with Rivian last summer. Software updates are also revenue opportunities in themselves. Accenture predicts that by the 2040s, digital services could generate up to 3.5 trillion dollars a year for car manufacturers, representing 40% of total revenues, compared to 3% today. The possibilities range from upgrading to heated seats and automatic parking to allowing drivers to buy high-quality food, fuel and entertainment directly from inside the vehicle. But that lucrative future will have to wait until the automotive industry masters the art of seamless software updates. The continuation of the original article via the Financial Times can be read here. 

Every year, dozens of heavy and light-duty cars are flagged for safety problems so serious that they require an immediate repair to correct a known defect. The number of recalls, as well as the number of vehicles affected, has been increasing over the last few decades - in 2023 alone, more than 30 million vehicles were recalled. According to US statistics, more and more safety recalls reveal the need to fix an electronic problem: Software-related malfunctions now account for more than 1 in 5 car recalls, according to an analysis released earlier this year of a decade of National Highway Traffic Safety Administration recall data by the law firm DeMayo Law. A separate estimate by Envorso, an American consulting firm specializing in software strategy for the automotive sector, highlighted an even more dramatic impact: The total number of vehicles affected by recalls related to software errors jumped from almost 15% of all vehicles recalled in 2023, to almost 42% of all vehicles recalled so far this year. In other words, more than 12 million vehicles were recalled due to software problems by the end of October. Earlier this year, Stellantis recalled more than one million vehicles in the US due to a software problem that prevented rear-view cameras from working properly. An investigation by the Detroit Free Press, published earlier this year, also revealed that millions of used and aging cars currently on US roads are not being repaired, despite dangerous defects identified by car manufacturers and the federal government. The investigation also found that the manufacturers of these cars are making little progress in repairing their older models with safety problems, putting a growing and vulnerable group of drivers at unnecessary risk. The continuation of the original article via Detroir Free Press can be read here. 

In Germany, a software error affected the state elections in Saxony, leading to a miscalculation of the new parliamentary seats. The state's electoral administration has now clarified the situation. The software glitch in the calculation of the distribution of seats in Saxony's new state parliament has been corrected, and this error had no effect on the provisional election result, according to the state election administration. According to the preliminary results, the CDU achieved a result of 31.9%; with the AfD just behind with 30.6% and BSW achieving 11.8% from the start. The SPD got 7.3% and the Greens 5.1%. The Left Party fell to 4.5% and the FDP to 0.9%. The decision on the distribution of seats in the 8th Saxony State Parliament will be taken by the state election commission after the official final result, which is still pending, the administration added. However, due to the recalculation after the crash, the AfD will most likely not have a so-called "blocking minority" in the state. The party has launched an investigation - "If there are any irregularities, we will take legal action," said Jörg Urban, the leader of the AfD's parliamentary and state group in Saxony, demanding a precise analysis of the error. A "blocking minority" means that a party has more than a third of the seats in the state parliament. In this case, it can prevent certain state laws that are passed with a two-thirds majority of all MPs. In Saxony, as in other federal states, constitutional judges and the president of the Court of Auditors, for example, are elected by a two-thirds majority of MPs. This means that certain positions could not be filled without the approval of the AfD, which could also have prevented the state parliament from dissolving itself. The original article via Diesachen can be read here. 

Volvo recently announced the recall of more than 72,000 electric vehicles due to a software error. According to the Swedish giant's press release, these EX30 model vehicles may accidentally display a "test screen" on the central monitor, obscuring the normal driving statistics displayed, including the speedometer and infotainment features. The exact cause of the problem has not yet been revealed. The bug was first detected during last month, when Volvo announced a recall of 1,255 vehicles, specifically in Australia. "Due to a software error, the infotainment unit's display may enter a test mode during vehicle start-up. This may prevent important information, such as vehicle speed, from being displayed," reads the Australian recall. "Failure to display important information could potentially increase the risk of injury or death to vehicle occupants and other road users." In fact, what makes this error especially problematic is that, unlike almost all other cars, all the statistics and information on these Volvo models, such as speed, are located only on the central display. For this reason, when an error of this nature occurs on the test screen, drivers are left without knowing exactly how fast they are going. Fortunately for EX30 owners, it won't be necessary to take their vehicles to the workshop or dealers to have the error corrected. An update, called version 1.3.1, is now available for anyone to download and install. This is not the first time that Volvo has encountered software problems in its latest cars. According to Volvo's public statements, the top-of-the-range EX90 was delayed by half a year just to concentrate on software development. The stakes are high when it comes to software and potential problems, especially when important components of a vehicle depend directly on the software to function properly. The original article via TheRegister can be read here. 

The US Food and Drug Administration (FDA) recently announced a recall of the highest severity level for a mobile application connected to an insulin pump. The application, the t:connect Mobile App iOS v2.7 from Tandem Diabetes Care, was recalled due to a bug that affected its communication with the t:slim X2 insulin pump. This detected software error could put diabetes patients, who rely on the app to control their insulin levels, at serious health risk. The FDA has advised patients to stop using the affected version of the app for the time being, and to return to using the insulin pump's integrated user interface until the problem is resolved. The company Tandem Diabetes Care is already fixing the problem and is expected to make a corrected software update available soon. In the meantime, users have been encouraged to keep a close eye on their glucose levels and consult their healthcare professionals about their insulin management. In the analysis of the problem in question, it was observed that this application - intended to be synchronized with the t:slim X2 insulin pump - stops and restarts abruptly, which can lead to rapid depletion of the pump's battery and users may not be able to access or control it via the application. In these situations, interruptions in insulin administration can occur, posing serious health problems for patients dependent on the pump. The original article via BaselineMag can be read here. 

Last week Apple released the latest update to its operating system, iOS 17.5, and although this update didn't bring with it many new features, its release was marked by a software error that causes old photos to reappear in the gallery, even though they have already been deleted. The first reports of this problem appeared on social media, especially on Reddit, where some users expressed their surprise when they realized that they had found old photos, which had already been deleted years ago, marked as "recently uploaded" in iCloud. Another user even shared a similar episode: "I have four photos from 2010 that keep showing up as the last photos uploaded to iCloud. I've deleted them several times". "I had a photo of a concert taken with my Canon camera, which reappeared in my phone's library as if it had been added today" - added another user. It's not clear why this problem has occurred, but given that some of the photos were apparently taken years ago, it can't be a problem of recently deleted photos not being deleted. In Apple's "Photos" application, deleted photos and videos are kept in the "Deleted" album for 30 days, so that users can recover them or permanently remove them from all devices.Still, the latest reports indicate that this could be an indexing bug, corruption of the photo library or a synchronization problem between local devices and iCloud Photos. Another possibility is that, in trying to fix a photo synchronization bug that occurred in iOS 17.3, Apple inadvertently caused a new synchronization problem that may involve iCloud backups. Some users running iOS 17.5 developer beta 4 have previously reported similar experiences. The original articles via PPLWare and Tom's Guide can be read here and here.

For those wishing to progress in their professional careers, here are three tips to help you stand out in the world of Software Testing: 1. More and more companies are demanding ISTQB® software testing certification for tester/QA roles. So if you don't already have an ISTQB® Foundation Level certification, don't waste any more time! This certification is mandatory before any other, and can really help boost your career path, enabling you to progress in your current company, or even get a new job. 2. Having an ISTQB® Foundation Level certification is the first step in the right direction, however, companies like their employees to evolve in their knowledge, and for this reason, you should also look for other ISTQB® certifications. Fortunately, PSTQB has all the available ISTQB® certifications at its disposal: not only those focused on specific areas, such as the ISTQB® CTFL Mobile Application Tester or even the ISTQB® CTFL Gambling Industry Tester; but also the more common ones, such as ISTQB® CTFL Agile Testing; and even the most recent one, which has aroused a lot of curiosity in the community, such as ISTQB® CTFL AI Testing. On the other hand, you can also take more advanced levels if your career requires it: in this case, ISTQB® CTAL Test Manager and ISTQB® CTAL Test Analyst, or even ISTQB® Techincal Test Analyst are good examples of steps to consider. (3) If you are interested in securing an ISTQB® certification, do so through PSTQB, with the support of an authorized training entity, or even independently if you wish. If you are successful, don't forget to update your CV and profile on professional social networks, as well as keeping in touch with other testers/QAs on the market. Original article translated and adapted from the American Software Testing Qualifications Board (ASTQB).

According to reports on social networks and forums, in recent months a software error has affected PlayStation Network (PSN) users, causing their games to be removed from their transaction history, making it impossible to use them. This problem was initially detected and exposed by a user on the Reddit social network. "In recent months, there has been an error affecting a relatively small number of PSN users," the post begins. The bug allegedly involves unlinking games purchased and titles added to your library via PlayStation Plus (PS+) from your transaction history. Specifically, this bug seems to be related to game licenses, which caused players to receive the error message CE-117773-6 when using them. According to the author of the original post, affected users may notice that their transaction history appears to be working correctly, however, the "Purchased" tab only shows the titles that were added after the error - "When trying to download, you will be asked to buy/add it on PS+, but if you try to do that, the system will tell you that you already have the content." In practice, according to this user, the installed games affected by the bug appear with a padlock icon and are not launched. Since it was published, the post has received thousands of reactions and hundreds of comments. "We need legislators to pass laws that protect consumer rights when it comes to digital goods," said another user. It's true that digital property has a number of advantages over physical games, being quicker to load and avoiding the accumulation/storage of disks. Nevertheless, they have a major drawback, since they are subject to companies being able to withdraw access to games at any time. This is not the case, but vulnerability to errors and glitches have prevented people from temporarily accessing their games. On the other hand, there were those who defended Sony, saying that all software is subject to bugs at any time - "There is no widely used software that doesn't have bugs," reads the same post. The author of the original thread also offered some tips to some users who may be affected by the supposed error: "My recommendation for anyone who receives an error message when trying to launch a game that was previously released normally is to first go to Playstation.com and check your games library - "Take a look at the "Purchases" tab and make sure it matches your complete history of games purchased/added on PS+", he added. He also left a warning: "If anything looks wrong, don't run the 'Restore Licenses' command on your console." The US Sun contacted Sony for comment, but has not yet received a reply. The original article via TheSun and USTimesPost can be read here and here.