Dushyant Chautala, the friend-turned-foe of the BJP who is out to fell the government, should police his party, sources have indicated.

Amid Haryana Crisis, 4 MLAs Of Dushyant Chautala Meet BJP's ML Khattar

Donald Trump is heading into the most perilous phase of his hush money trial aside from the moment when the jury retires to consider its verdict.

Analysis: Critical days of Trump trial will test whether he can exercise discipline and restraint | CNN Politics

Predicted victory for nationalist VMRO-DPMNE may stir tensions with EU neighbours Greece and Bulgaria.

North Macedonia’s opposition set for big election wins | Elections News | Al Jazeera

OTTAWA — The federal government will test its capacity to issue emergency alerts today. That means Canadians in most provinces and territories will receive a test alert on their cellphones, as well as through TV and radio broadcasts. The sole exception is Ontario, where the test will take ...

Most of Canada to receive emergency alert test today

Canada&#x27;s national public alert system is running tests on television, radio and compatible wireless devices across most of the country on May 8.

There's a test of the national emergency alert system in most of Canada Wednesday | CBC News

The City of Montreal is slated to test out its annual warning siren test Wednesday.

Montreal to carry out annual warning siren test | CTV News

The federal government will test its capacity to issue emergency alerts today, with the exception of Ontario, where the test will take place on May 15.

Cellphone emergency alert system testing in Canada | CTV News

Mastercard Inc. is joining with some of the largest US banks to test shared-ledger technology that would allow the common settlement of tokenized assets such as commercial-bank money as well as Treasury and investment-grade debt securities.

Mastercard, Citi, JPMorgan Test Ledger for Settling Bank Money - BNN Bloomberg

Montreal will test population alert sirens between 9 a.m. and 3 p.m. on Wednesday, the city says in a news release. The exercise aims to raise awareness among residents who live near 10 factories that could have a toxic leak of some kind.

Montreal to test alert sirens throughout the day | CBC News

Here is a roundup of stories from The Canadian Press designed to bring you up to speed on what you need to know today… Most of Canada to receive emergency alert test The federal government will test its capacity to issue emergency alerts today. That means Canadians in most provinces and ...

In the news today: Emergency alert test, Drake shooting investigation

2TEST

2test

Table of Links Abstract and 1 Introduction 1.1 Related literature Types of Metrics and Their Hypothesis and 2.1 Types of metrics
2.2 Hypotheses for different types of metrics


Type I and Type II Error Rates for Decision Rules including Superiority and Non-Inferiority Tests
3.1 The composite hypotheses of superiority and non-inferiority tests
3.2 Bounding the type I and type II error rates for UI and IU testing
3.3 Bounding the error rates for a decision rule including both success and guardrail metrics
3.4 Power corrections for non-inferiority testing


Extending the Decision Rule with Deterioration and Quality Metrics


Monte Carlo Simulation Study
5.1 Results


Discussion and Conclusions APPENDIX A: IMPROVING THE EFFICIENCY OF PROPOSITION 4.1 WITH ADDITIONAL ASSUMPTIONS APPENDIX B: EXAMPLES OF GLOBAL FALSE AND TRUE POSITIVE RATES APPENDIX C: A NOTE ON SEQUENTIAL TESTING OF DETERIORATION APPENDIX D: USING NYHOLT’S METHOD OF EFFICIENT NUMBER OF INDEPENDENT TESTS Acknowledgments and References APPENDIX B: EXAMPLES OF GLOBAL FALSE AND TRUE POSITIVE RATES APPENDIX C: A NOTE ON SEQUENTIAL TESTING OF DETERIORATION In the previous sections it is shown that if a fixed horizon test is used, the type I error rate of the non-inferiority and superiority tests are not affected by adding deterioration tests under mild conditions on β and α_. However, deterioration tests are typically added to ensure that the experiment can be aborted if some metrics start to deteriorate. To be able t maintain the type I error rate for the deterioration tests (α_), this requires using sequential tests for the deterioration tests. Sequential deterioration tests add complexity to the error rate calculations. This follows because even under conditions where the rejection regions for the deterioration and the superiority/non-inferiority tests are not overlapping at the last time point, it is possible that the deterioration test is significant at a previous intermittent analysis even in the case where the superiority or non-inferiority test is significant when the experiment is concluded. It is difficult to bound these risks without referring to a specific test. E.g., in the Group Sequential Test (GST) literature, stopping if a treatment effect is going in the wrong direction is possible using so called futility bounds. It is well known that the incorporation of such bounds decrease the type I error rate and power for the superiority test. If one commits to always stopping if futility bounds are crossed, so-called "binding futility bounds", one can adjust the bounds for the superiority test to achieve the intended type I error rate. As we will show below, in practice, adding sequential deterioration tests will only mildly affect the rates. Here, we simply estimate the type I error rate and power of the superiority test and non-inferiority test with deterioration, respectively, by Monte Carlo simulation. One hundred intermittent analyses are performed for the deterioration test using GST[2]. The alternatives and NIM are selected to yield 80% power for the fixed-horizon tests without deterioration. One million replications were performed for each setting. Table 9 displays the results. For success metrics, the results indicate that using deterioration tests in addition to the superiority test for success metrics imposes negligible conservativeness under the null and the alternative. Under the non-inferiority null hypothesis, the type I error rate decreases slightly due to deterioration, but to a degree without much practical relevance. The power of the deterioration test is 72%, which is lower than 80% because the deterioration test uses a GST test with a 100 intermittent analyses which decreases the overall power as compared to a fixed horizon test. Under the non-inferiority alternative, the rejection rate of the deterioration test decreases to the expected around 5%, and the power of the non-inferiority is not practically affected by the deterioration test. It is of course natural to consider sequential tests also for quality tests, such as sample ratio mismatch. However, since these tests tends to separate from the success and guardrail metrics, using sequential tests has no implications. As long as the quality test that are used are valid, i.e., bounds the type I error rates, the propositions apply also with sequential tests for the quality metrics. In the next section we formalize the inclusion of quality metrics in the decision rule. Authors:
(1) Mårten Schultzberg, Experimentation Platform team, Spotify, Stockholm, Sweden;
(2) Sebastian Ankargren, Experimentation Platform team, Spotify, Stockholm, Sweden;
(3) Mattias Frånberg, Experimentation Platform team, Spotify, Stockholm, Sweden. This paper is available on arxiv under CC BY 4.0 DEED license. [2] The simulation code is available in the online supplementary material, and it is easy to to exchange the GST for any other sequential test. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 1.1 Related literature 1.1 Related literature Types of Metrics and Their Hypothesis and 2.1 Types of metrics
2.2 Hypotheses for different types of metrics Type I and Type II Error Rates for Decision Rules including Superiority and Non-Inferiority Tests
3.1 The composite hypotheses of superiority and non-inferiority tests
3.2 Bounding the type I and type II error rates for UI and IU testing
3.3 Bounding the error rates for a decision rule including both success and guardrail metrics
3.4 Power corrections for non-inferiority testing Extending the Decision Rule with Deterioration and Quality Metrics Monte Carlo Simulation Study
5.1 Results Discussion and Conclusions Types of Metrics and Their Hypothesis and 2.1 Types of metrics 2.2 Hypotheses for different types of metrics Types of Metrics and Their Hypothesis and 2.1 Types of metrics Types of Metrics and Their Hypothesis and 2.1 Types of metrics 2.2 Hypotheses for different types of metrics 2.2 Hypotheses for different types of metrics Type I and Type II Error Rates for Decision Rules including Superiority and Non-Inferiority Tests 3.1 The composite hypotheses of superiority and non-inferiority tests 3.2 Bounding the type I and type II error rates for UI and IU testing 3.3 Bounding the error rates for a decision rule including both success and guardrail metrics 3.4 Power corrections for non-inferiority testing Type I and Type II Error Rates for Decision Rules including Superiority and Non-Inferiority Tests Type I and Type II Error Rates for Decision Rules including Superiority and Non-Inferiority Tests 3.1 The composite hypotheses of superiority and non-inferiority tests 3.1 The composite hypotheses of superiority and non-inferiority tests 3.2 Bounding the type I and type II error rates for UI and IU testing 3.2 Bounding the type I and type II error rates for UI and IU testing 3.3 Bounding the error rates for a decision rule including both success and guardrail metrics 3.3 Bounding the error rates for a decision rule including both success and guardrail metrics 3.4 Power corrections for non-inferiority testing 3.4 Power corrections for non-inferiority testing Extending the Decision Rule with Deterioration and Quality Metrics Extending the Decision Rule with Deterioration and Quality Metrics Extending the Decision Rule with Deterioration and Quality Metrics Monte Carlo Simulation Study 5.1 Results Monte Carlo Simulation Study Monte Carlo Simulation Study 5.1 Results 5.1 Results Discussion and Conclusions Discussion and Conclusions Discussion and Conclusions APPENDIX A: IMPROVING THE EFFICIENCY OF PROPOSITION 4.1 WITH ADDITIONAL ASSUMPTIONS APPENDIX A: APPENDIX A: IMPROVING THE EFFICIENCY OF PROPOSITION 4.1 WITH ADDITIONAL ASSUMPTIONS APPENDIX B: EXAMPLES OF GLOBAL FALSE AND TRUE POSITIVE RATES APPENDIX B: APPENDIX B: EXAMPLES OF GLOBAL FALSE AND TRUE POSITIVE RATES APPENDIX C: A NOTE ON SEQUENTIAL TESTING OF DETERIORATION APPENDIX C: APPENDIX C: A NOTE ON SEQUENTIAL TESTING OF DETERIORATION APPENDIX D: USING NYHOLT’S METHOD OF EFFICIENT NUMBER OF INDEPENDENT TESTS APPENDIX D: APPENDIX D: USING NYHOLT’S METHOD OF EFFICIENT NUMBER OF INDEPENDENT TESTS Acknowledgments and References Acknowledgments and References APPENDIX B: EXAMPLES OF GLOBAL FALSE AND TRUE POSITIVE RATES APPENDIX C: A NOTE ON SEQUENTIAL TESTING OF DETERIORATION In the previous sections it is shown that if a fixed horizon test is used, the type I error rate of the non-inferiority and superiority tests are not affected by adding deterioration tests under mild conditions on β and α_. However, deterioration tests are typically added to ensure that the experiment can be aborted if some metrics start to deteriorate. To be able t maintain the type I error rate for the deterioration tests (α_), this requires using sequential tests for the deterioration tests. Sequential deterioration tests add complexity to the error rate calculations. This follows because even under conditions where the rejection regions for the deterioration and the superiority/non-inferiority tests are not overlapping at the last time point, it is possible that the deterioration test is significant at a previous intermittent analysis even in the case where the superiority or non-inferiority test is significant when the experiment is concluded. It is difficult to bound these risks without referring to a specific test. E.g., in the Group Sequential Test (GST) literature, stopping if a treatment effect is going in the wrong direction is possible using so called futility bounds. It is well known that the incorporation of such bounds decrease the type I error rate and power for the superiority test. If one commits to always stopping if futility bounds are crossed, so-called "binding futility bounds", one can adjust the bounds for the superiority test to achieve the intended type I error rate. As we will show below, in practice, adding sequential deterioration tests will only mildly affect the rates. Here, we simply estimate the type I error rate and power of the superiority test and non-inferiority test with deterioration, respectively, by Monte Carlo simulation. One hundred intermittent analyses are performed for the deterioration test using GST[2]. The alternatives and NIM are selected to yield 80% power for the fixed-horizon tests without deterioration. One million replications were performed for each setting. Table 9 displays the results. For success metrics, the results indicate that using deterioration tests in addition to the superiority test for success metrics imposes negligible conservativeness under the null and the alternative. Under the non-inferiority null hypothesis, the type I error rate decreases slightly due to deterioration, but to a degree without much practical relevance. The power of the deterioration test is 72%, which is lower than 80% because the deterioration test uses a GST test with a 100 intermittent analyses which decreases the overall power as compared to a fixed horizon test. Under the non-inferiority alternative, the rejection rate of the deterioration test decreases to the expected around 5%, and the power of the non-inferiority is not practically affected by the deterioration test. It is of course natural to consider sequential tests also for quality tests, such as sample ratio mismatch. However, since these tests tends to separate from the success and guardrail metrics, using sequential tests has no implications. As long as the quality test that are used are valid, i.e., bounds the type I error rates, the propositions apply also with sequential tests for the quality metrics. In the next section we formalize the inclusion of quality metrics in the decision rule. Authors: (1) Mårten Schultzberg, Experimentation Platform team, Spotify, Stockholm, Sweden; (2) Sebastian Ankargren, Experimentation Platform team, Spotify, Stockholm, Sweden; (3) Mattias Frånberg, Experimentation Platform team, Spotify, Stockholm, Sweden. Authors: Authors: (1) Mårten Schultzberg, Experimentation Platform team, Spotify, Stockholm, Sweden; (2) Sebastian Ankargren, Experimentation Platform team, Spotify, Stockholm, Sweden; (3) Mattias Frånberg, Experimentation Platform team, Spotify, Stockholm, Sweden. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv available on arxiv [2] The simulation code is available in the online supplementary material, and it is easy to to exchange the GST for any other sequential test.

Evaluating False Positives and Sequential Testing in Experimentation

Pull Request Testing on Kubernetes: How to Test Locally and on GitHub Workflows

Authors:
(1) Howard Zhong, MIT CSAIL (howardzh@mit.edu);
(2) Mark Hamilton, MIT CSAIL, Microsoft (markth@mit.edu). Table of Links Abstract and 1 Introduction 2 Methodology 3 Results 3.1 CryptoPunks 3.2 Aggregate NFT Market 4 Discussion 5. Conclusion/ Acknowledgements/ References A Appendix A.1 Implementation Details A.2 Detailed NFT Information & A.3 Google NFT Searches Map A.1 Implementation Details We elaborate on the methods and the implementation details. This sections follows the structure Section 2. A.1.1 Initial Data Collection Our dataset only includes NFTs transacted on OpenSea, which is the primary marketplace for NFTs on the Ethereum blockchain. We query the OpenSea “v1/collections” endpoint at the end of November 2022 [15] to retrieve collection metadata as well as each individual NFT’s metadata and last sale price. We choose 790 collection names from the Kaggle Ethereum NFTs dataset [11] and NFTs from the top 30-day and all-time OpenSea volume leaderboard around November 2021. Most collections have around 5,000 to 10,000 items, and our queries yield around 70-80% of the data as the other 20-30% do not have transactions. After querying the Application Programming Interface (API) using a script written with the PySpark framework [17] on Databricks, we create a dataframe containing each NFT’s collection name, id, sale information, metadata, and image url. We then loop through this dataframe with multiple workers to download the images in parallel. In the end, we obtain a dataset of about ∼ 2.5 NFTs, each that have been transacted upon. A.1.2 Retrieving Race and Gender Labels To get gender-labelled data, we select collections that have metadata with the words “male” and “female” to find collections where at least 50% of the images have gender labels. We filter out collections that have more than 75% male or female to avoid rarity factors affecting the price. We find a total of 44 such collections with gender labels that satisfy the criteria. These collections with gender labels are It is more challenging to determine the race of an NFT collection because most collections do not directly annotate this information. For the CryptoPunks collection, we label each NFT based on the frequencies of the four different pixel values representing the four different skin tones as displayed in Figure 6. The above process was inspired by [5]. For our analysis, we group darkest and mid as Dark and lighter and lightest as Light. For other collections, we were unable to retrieve race labels from the metadata. We also attempted to find race labels for a subset of the 44 collections with gender labels with the criteria that there were a high proportion of items that could be categorized as either dark or light skinned. We filtered out collections that have more than 75% light-skinned or dark-skinned to avoid rarity factors affecting the price. This required manual review because most collections do not have easy-to-search race labels in the metadata, or even way to categorize race. For Avastar, we categorized “Amber Brown” as dark-skinned and “Pale Pink” as light-skinned in the “skin tone” attribute. For Dynamic Duelers, we categorized “Black” as dark-skinned and “White” as lightskinned in the “Skin color” attribute. A.1.3 Statistical Tools to Analyze Bias in Gender and Race We detail the statistical methods used to analyze the bias in NFT pricing for gender and race. Specifically, we go into more detail about the implementation and underlying assumptions of these tests. Unpaired t-test assumes independence of observations and each point belongs to either male or female


the variances of male and female prices are equal for the population


the prices follows a normal distribution


no significant outliers in each group The unpaired t-test is robust to all but large deviation from these assumptions. Assumption 1 and 2 are satisfied, but 3 and 4 require more careful consideration. Log Transformation: For assumption 3, with rare NFTs worth significantly more than common NFTs, NFT price distributions tend to follow a power law distribution [14]. Because it’s well known that stock prices follow a log-normal distribution [1], we apply the same transformation and found log of price tended to be closer to a normal distribution. We thus decided to also run the t-test on the log of prices, which we refer to as log t-test. Outlier Trimming: For assumption 4, as outliers may occur due to very high selling prices for rare NFTs or very low selling prices due to humans errors while listing, we address this issue by Winsorization [19], or trimming outliers past a certain percentile. Specifically, we report t-test results while trimming both left and right tails of the distribution at 0.1%, 1%, 2.5%, and 5% percentiles. Paired t-test: In addition to the unpaired t-test for independent samples, we also run a paired t-test for two dependent samples in order to better isolate the male versus female price difference while fixing time. Specifically, we calculate t-statistics on the paired difference of male and female prices marked to the daily mean price and the weekly mean price of the NFT. Assumptions 1 and 2 are now (1) male - female price must be continuous and (2) observations are independent of one another. Assumptions 3 and 4 from unpaired test remain the same and. We address assumptions 3 and 4 with the log-transformation and Winsorization, as described earlier. The approach described above is also used to compare the prices of lighter-skinned and darkerskinned CryptoPunks. We utilize the SciPy Python package [21] to implement both types of t-tests. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Howard Zhong, MIT CSAIL (howardzh@mit.edu); (2) Mark Hamilton, MIT CSAIL, Microsoft (markth@mit.edu). Authors: Authors: (1) Howard Zhong, MIT CSAIL (howardzh@mit.edu); (2) Mark Hamilton, MIT CSAIL, Microsoft (markth@mit.edu). Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 Methodology 2 Methodology 3 Results 3.1 CryptoPunks 3.1 CryptoPunks 3.2 Aggregate NFT Market 3.2 Aggregate NFT Market 4 Discussion 4 Discussion 5. Conclusion/ Acknowledgements/ References Conclusion/ Acknowledgements/ References A Appendix A Appendix A.1 Implementation Details A.1 Implementation Details A.2 Detailed NFT Information & A.3 Google NFT Searches Map A.2 Detailed NFT Information & A.3 Google NFT Searches Map A.1 Implementation Details We elaborate on the methods and the implementation details. This sections follows the structure Section 2. A.1.1 Initial Data Collection Our dataset only includes NFTs transacted on OpenSea, which is the primary marketplace for NFTs on the Ethereum blockchain. We query the OpenSea “v1/collections” endpoint at the end of November 2022 [15] to retrieve collection metadata as well as each individual NFT’s metadata and last sale price. We choose 790 collection names from the Kaggle Ethereum NFTs dataset [11] and NFTs from the top 30-day and all-time OpenSea volume leaderboard around November 2021. Most collections have around 5,000 to 10,000 items, and our queries yield around 70-80% of the data as the other 20-30% do not have transactions. After querying the Application Programming Interface (API) using a script written with the PySpark framework [17] on Databricks, we create a dataframe containing each NFT’s collection name, id, sale information, metadata, and image url. We then loop through this dataframe with multiple workers to download the images in parallel. In the end, we obtain a dataset of about ∼ 2.5 NFTs, each that have been transacted upon. A.1.2 Retrieving Race and Gender Labels To get gender-labelled data, we select collections that have metadata with the words “male” and “female” to find collections where at least 50% of the images have gender labels. We filter out collections that have more than 75% male or female to avoid rarity factors affecting the price. We find a total of 44 such collections with gender labels that satisfy the criteria. These collections with gender labels are It is more challenging to determine the race of an NFT collection because most collections do not directly annotate this information. For the CryptoPunks collection, we label each NFT based on the frequencies of the four different pixel values representing the four different skin tones as displayed in Figure 6. The above process was inspired by [5]. For our analysis, we group darkest and mid as Dark and lighter and lightest as Light. For other collections, we were unable to retrieve race labels from the metadata. We also attempted to find race labels for a subset of the 44 collections with gender labels with the criteria that there were a high proportion of items that could be categorized as either dark or light skinned. We filtered out collections that have more than 75% light-skinned or dark-skinned to avoid rarity factors affecting the price. This required manual review because most collections do not have easy-to-search race labels in the metadata, or even way to categorize race. For Avastar, we categorized “Amber Brown” as dark-skinned and “Pale Pink” as light-skinned in the “skin tone” attribute. For Dynamic Duelers, we categorized “Black” as dark-skinned and “White” as lightskinned in the “Skin color” attribute. A.1.3 Statistical Tools to Analyze Bias in Gender and Race We detail the statistical methods used to analyze the bias in NFT pricing for gender and race. Specifically, we go into more detail about the implementation and underlying assumptions of these tests. Unpaired t-test assumes Unpaired t-test independence of observations and each point belongs to either male or female the variances of male and female prices are equal for the population the prices follows a normal distribution no significant outliers in each group independence of observations and each point belongs to either male or female independence of observations and each point belongs to either male or female the variances of male and female prices are equal for the population the variances of male and female prices are equal for the population the prices follows a normal distribution the prices follows a normal distribution no significant outliers in each group no significant outliers in each group The unpaired t-test is robust to all but large deviation from these assumptions. Assumption 1 and 2 are satisfied, but 3 and 4 require more careful consideration. Log Transformation: For assumption 3, with rare NFTs worth significantly more than common NFTs, NFT price distributions tend to follow a power law distribution [14]. Because it’s well known that stock prices follow a log-normal distribution [1], we apply the same transformation and found log of price tended to be closer to a normal distribution. We thus decided to also run the t-test on the log of prices, which we refer to as log t-test. Log Transformation: Outlier Trimming: For assumption 4, as outliers may occur due to very high selling prices for rare NFTs or very low selling prices due to humans errors while listing, we address this issue by Winsorization [19], or trimming outliers past a certain percentile. Specifically, we report t-test results while trimming both left and right tails of the distribution at 0.1%, 1%, 2.5%, and 5% percentiles. Outlier Trimming: Paired t-test: In addition to the unpaired t-test for independent samples, we also run a paired t-test for two dependent samples in order to better isolate the male versus female price difference while fixing time. Specifically, we calculate t-statistics on the paired difference of male and female prices marked to the daily mean price and the weekly mean price of the NFT. Assumptions 1 and 2 are now (1) male - female price must be continuous and (2) observations are independent of one another. Assumptions 3 and 4 from unpaired test remain the same and. We address assumptions 3 and 4 with the log-transformation and Winsorization, as described earlier. Paired t-test: The approach described above is also used to compare the prices of lighter-skinned and darkerskinned CryptoPunks. We utilize the SciPy Python package [21] to implement both types of t-tests. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Behind the Scenes: Data Collection and Statistical Tools for NFT Bias Study

Authors:
(1) Philipp Straubinger, University of Passau, Germany;
(2) Gordon Fraser, University of Passau, Germany. Table of Links Abstract and 1 Introduction 2.1 Software Testing 2.2 Gamification of Software Testing 3 Gamifying Continuous Integration and 3.1 Challenges in Teaching Software Testing 3.2 Gamification Elements of Gamekins 3.3 Gamified Elements and the Testing Curriculum 4 Experiment Setup and 4.1 Software Testing Course 4.2 Integration of Gamekins and 4.3 Participants 4.4 Data Analysis 4.5 Threats to Validity 5.1 RQ1: How did the students use Gamekins during the course? 5.2 RQ2: What testing behavior did the students exhibit? 5.3 RQ3: How did the students perceive the integration of Gamekins into their projects? 6 Related Work 7 Conclusions, Acknowledgments, and References ABSTRACT Testing plays a crucial role in software development, and it is essential for software engineering students to receive proper testing education. However, motivating students to write tests and use automated testing during software development can be challenging. To address this issue and enhance student engagement in testing when they write code, we propose to incentivize students to test more by gamifying continuous integration. For this we use Gamekins, a tool that is seamlessly integrated into the Jenkins continuous integration platform and uses game elements based on commits to the source code repository: Developers can earn points by completing test challenges and quests generated by Gamekins, compete with other developers or teams on a leaderboard, and receive achievements for their test-related accomplishments. In this paper, we present our integration of Gamekins into an undergraduate-level course on software testing. We observe a correlation between how students test their code and their use of Gamekins, as well as a significant improvement in the accuracy of their results compared to a previous iteration of the course without gamification. As a further indicator of how this approach improves testing behavior, the students reported enjoyment in writing tests with Gamekins. CCS CONCEPTS • Software and its engineering → Software testing and debugging; • Social and professional topics → Software engineering education KEYWORDS Software Testing, Gamification, Continuous Integration, Education ACM Reference Format: Philipp Straubinger and Gordon Fraser. 2024. Gamifying a Software Testing Course with Continuous Integration. In 46th International Conference on Software Engineering: : Software Engineering Education and Training (ICSESEET ’24), April 14–20, 2024, Lisbon, Portugal. ACM, New York, NY, USA, 12 pages. https://doi.org/10.1145/3639474.3640054 1 INTRODUCTION Software testing is a well-established concept and is extensively used in the industry [13]. However, despite the availability of various tools that facilitate the testing process, such as testing support in integrated development environments (IDE) [26] and automated test execution in continuous integration (CI) platforms [8], testing is often overlooked in practice. Speculated reasons for this include developers’ lack of motivation to engage in testing activities and a lack of education in software testing [14, 30, 41, 49, 50]. Although the often inadequate treatment of testing in higher education [41] has recently been countered with a growing recognition of the importance of testing [9, 29, 35], this is nevertheless hampered by learners just like developers tending to perceive testing as tedious and boring [32]. As a result, the industry suffers significant losses due to inadequate software quality and insufficient testing [31]. Gamification techniques provide an opportunity to motivate students to test despite their perception of it being boring or tedious. Gamification involves incorporating elements commonly found in games, such as leaderboards and achievements, into nongame contexts [15]. It has been demonstrated that this approach helps engage students in software engineering education [24], for example by gamifying lectures or tools to teach software testing [7, 12, 16, 22, 36]. However, in order for students to internalize testing and establish it as an integral part of their development approach, we argue that seamless integration of gamification of testing into the software development process is necessary. In order to achieve this, we integrate gamification into continuous integration (CI) systems used by students. Specifically, we use Gamekins [47], a plugin designed for the widely used CI platform Jenkins[1], which seamlessly integrates gamification into the software development workflow. By analyzing source code and test results, Gamekins identifies areas where testing can be improved based on code coverage [53] or mutation analysis [28] and then incentivizes improvement using gamification concepts such as challenges and quests, rewarding good testing with points, achievements, and leaderboard rankings. We evaluated the benefits of integrating Gamekins in an undergraduate software testing course, investigating its impact on the course’ learning objectives and student behavior. In detail, the contributions of this paper are as follows: • We propose the use of gamification as a means to incentivize and reward testing activities in CI. • We introduceGamekins as a tool to be used in an undergraduate-level software testing course. • We empirically evaluate the effects of integrating Gamekins into the software testing course, comparing to a previous cohort without gamification and surveying the students. The results of the study demonstrate a correlation between students’ testing behavior and the use of Gamekins, as well as a significant improvement in correct results compared to the previous edition of the course, where no gamification was used on the same assignments. While not all aspects of Gamekins were universally liked by students, overall, they enjoyed its use throughout the course, confirming that Gamekins is a viable teaching tool. This paper is available on arxiv under CC BY-SA 4.0 DEED license. [1] https://www.jenkins.io/ Authors: (1) Philipp Straubinger, University of Passau, Germany; (2) Gordon Fraser, University of Passau, Germany. Authors: Authors: (1) Philipp Straubinger, University of Passau, Germany; (2) Gordon Fraser, University of Passau, Germany. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2.1 Software Testing 2.1 Software Testing 2.2 Gamification of Software Testing 2.2 Gamification of Software Testing 3 Gamifying Continuous Integration and 3.1 Challenges in Teaching Software Testing 3 Gamifying Continuous Integration and 3.1 Challenges in Teaching Software Testing 3.2 Gamification Elements of Gamekins 3.2 Gamification Elements of Gamekins 3.3 Gamified Elements and the Testing Curriculum 3.3 Gamified Elements and the Testing Curriculum 4 Experiment Setup and 4.1 Software Testing Course 4 Experiment Setup and 4.1 Software Testing Course 4.2 Integration of Gamekins and 4.3 Participants 4.2 Integration of Gamekins and 4.3 Participants 4.4 Data Analysis 4.4 Data Analysis 4.5 Threats to Validity 4.5 Threats to Validity 5.1 RQ1: How did the students use Gamekins during the course? 5.1 RQ1: How did the students use Gamekins during the course? 5.2 RQ2: What testing behavior did the students exhibit? 5.2 RQ2: What testing behavior did the students exhibit? 5.3 RQ3: How did the students perceive the integration of Gamekins into their projects? 5.3 RQ3: How did the students perceive the integration of Gamekins into their projects? 6 Related Work 6 Related Work 7 Conclusions, Acknowledgments, and References 7 Conclusions, Acknowledgments, and References ABSTRACT Testing plays a crucial role in software development, and it is essential for software engineering students to receive proper testing education. However, motivating students to write tests and use automated testing during software development can be challenging. To address this issue and enhance student engagement in testing when they write code, we propose to incentivize students to test more by gamifying continuous integration. For this we use Gamekins, a tool that is seamlessly integrated into the Jenkins continuous integration platform and uses game elements based on commits to the source code repository: Developers can earn points by completing test challenges and quests generated by Gamekins, compete with other developers or teams on a leaderboard, and receive achievements for their test-related accomplishments. In this paper, we present our integration of Gamekins into an undergraduate-level course on software testing. We observe a correlation between how students test their code and their use of Gamekins, as well as a significant improvement in the accuracy of their results compared to a previous iteration of the course without gamification. As a further indicator of how this approach improves testing behavior, the students reported enjoyment in writing tests with Gamekins. CCS CONCEPTS CCS CONCEPTS • Software and its engineering → Software testing and debugging; • Social and professional topics → Software engineering education • Software and its engineering → Software testing and debugging; • Social and professional topics → Software engineering education KEYWORDS KEYWORDS Software Testing, Gamification, Continuous Integration, Education ACM Reference Format: ACM Reference Format: Philipp Straubinger and Gordon Fraser. 2024. Gamifying a Software Testing Course with Continuous Integration. In 46th International Conference on Software Engineering: : Software Engineering Education and Training (ICSESEET ’24), April 14–20, 2024, Lisbon, Portugal. ACM, New York, NY, USA, 12 pages. https://doi.org/10.1145/3639474.3640054 1 INTRODUCTION Software testing is a well-established concept and is extensively used in the industry [13]. However, despite the availability of various tools that facilitate the testing process, such as testing support in integrated development environments (IDE) [26] and automated test execution in continuous integration (CI) platforms [8], testing is often overlooked in practice. Speculated reasons for this include developers’ lack of motivation to engage in testing activities and a lack of education in software testing [14, 30, 41, 49, 50]. Although the often inadequate treatment of testing in higher education [41] has recently been countered with a growing recognition of the importance of testing [9, 29, 35], this is nevertheless hampered by learners just like developers tending to perceive testing as tedious and boring [32]. As a result, the industry suffers significant losses due to inadequate software quality and insufficient testing [31]. Gamification techniques provide an opportunity to motivate students to test despite their perception of it being boring or tedious. Gamification involves incorporating elements commonly found in games, such as leaderboards and achievements, into nongame contexts [15]. It has been demonstrated that this approach helps engage students in software engineering education [24], for example by gamifying lectures or tools to teach software testing [7, 12, 16, 22, 36]. However, in order for students to internalize testing and establish it as an integral part of their development approach, we argue that seamless integration of gamification of testing into the software development process is necessary. In order to achieve this, we integrate gamification into continuous integration (CI) systems used by students. Specifically, we use Gamekins [47], a plugin designed for the widely used CI platform Jenkins[1], which seamlessly integrates gamification into the software development workflow. By analyzing source code and test results, Gamekins identifies areas where testing can be improved based on code coverage [53] or mutation analysis [28] and then incentivizes improvement using gamification concepts such as challenges and quests, rewarding good testing with points, achievements, and leaderboard rankings. We evaluated the benefits of integrating Gamekins in an undergraduate software testing course, investigating its impact on the course’ learning objectives and student behavior. In detail, the contributions of this paper are as follows: • We propose the use of gamification as a means to incentivize and reward testing activities in CI. • We introduceGamekins as a tool to be used in an undergraduate-level software testing course. • We empirically evaluate the effects of integrating Gamekins into the software testing course, comparing to a previous cohort without gamification and surveying the students. The results of the study demonstrate a correlation between students’ testing behavior and the use of Gamekins, as well as a significant improvement in correct results compared to the previous edition of the course, where no gamification was used on the same assignments. While not all aspects of Gamekins were universally liked by students, overall, they enjoyed its use throughout the course, confirming that Gamekins is a viable teaching tool. This paper is available on arxiv under CC BY-SA 4.0 DEED license. This paper is available on arxiv under CC BY-SA 4.0 DEED license. available on arxiv [1] https://www.jenkins.io/

Gamification Makes It Easier to Teach Software Testing – New Study Shows

Gamification maak dit makliker om sagtewaretoetsing te onderrig – nuwe studieprogramme

تُظهِر دراسة جديدة أن اللعبيّة تجعل تدريس اختبار البرمجيات أسهل

Gamification ukax Software yant’äw yatichañax juk’amp jasakiw – Machaq Yatxatäw uñacht’äwinaka

Gamification gør det nemmere at undervise i softwaretestning – nye undersøgelsesshows

La gamificación facilita la enseñanza de pruebas de software, según un nuevo estudio

गेमिफिकेशन से सॉफ्टवेयर परीक्षण सिखाना आसान हो गया है – नया अध्ययन दिखाता है

ゲーミフィケーションによりソフトウェアテストの指導が容易になる - 新しい研究結果

Gamification Esalaka Pete Koteya Testing ya Logiciel – Elakiseli ya sika ya boyekoli

Gamification Inoita Kuti Zvive nyore Kudzidzisa Software Kuedza - Nyowani Yekudzidza Inoratidza

Gamification таълим додани санҷиши нармафзорро осонтар мекунад - Намоишҳои нави таҳқиқот

Pinapadali ng Gamification ang Pagtuturo ng Software Testing – Mga Bagong Palabas sa Pag-aaral

Gamifikatsiya dasturiy ta'minotni sinovdan o'tkazishni o'rgatishni osonlashtiradi - yangi o'quv shoulari

A Semester-Long Experiment Shows Gamification Boosts Learning Outcomes in Software Testing Education

The need for safe, offline backup is driven by ransomware attacks, which I actually experienced in my company. However, there are also other kinds of needs to move files between workstations, home, and office computers, and there is a need to have backup in case of system crashes or accidental deletions. For such situations External USB memory/disk devices are irreplaceable. I like them because I can attach them to make a backup and later detach them and physically move them to a safe place, where they are definitely offline. My favorite backup method is very simple one: the usage of FreeFileSync app (high-quality freeware) that synchronizes directories. I keep all my work files on my work laptop in one root folder and sync periodically to an External USB device. In compliance with company rules, I keep all my External USB devices BitLocker encrypted and secured with the password needed to access the device. There are many sensitive company and personal documents I have there, so I definitely want them safe in case memory/disk device is lost, for example during commuting to/from the office. Over the years technology for External USB memory/disk backup changed, bringing always greater transfer speeds. I bought some latest External SSD-s, so I wanted to test them. 2 Test scenario setup Here are the basic testing conditions: I will use a new Lenovo laptop with the newest USB A and USB C ports
I will backup real life work files, around 49.4GB
I will backup them to the External USB memory/disk device of choice
External USB memory/disk device will be BitLocker encrypted
I will use FreeFileSync app (high-quality freeware) that synchronizes directories as a backup solution Here are the specs for the ports of my laptop: Here is the folder with real-life docs that I will backup: 3 Testing External 64GB USB Flash drive Device info: 64GB USB Flash drive
Kinston DataTraveler 3.0 USB
USB-A, 3.0 (5Gbps)
49.4GB transferred in 97min 15sec
Average speed of backup 8.66MBps=69.26Mbps 4 Testing External 1 TB USB HDD Device info: External 1 TB USB HDD
Toshiba 1 TB HDD
USB-A, 3.0 (5Gbps)
49.4GB transferred in 22min 28sec
Average speed of backup 37.5 MBps=300 Mbps 5 Testing External SSD 1 TB, USB 3.2 Gen2 Device info: External 1 TB SSD
Samsung PSSD T7 1TB
USB-C 3.2 Gen 2 (10Gbps)
49.4GB transferred in 4min 3sec
Average speed of backup 208 MBps=1664 Mbps 6 Testing External SSD 2 TB, USB 3.2 Gen2x2 Device info: External 2 TB SSD
Samsung PSSD T9 2TB
USB-C 3.2 Gen 2x2 (20Gbps)
49.4GB transferred in 2min 38sec
Average speed of backup 320 MBps=2560 Mbps 7 Conclusion So, here are actual practical speeds of backup in real-world situations: These values are measured in these conditions: used a new Lenovo laptop (December 2024) with the newest USB A and USB C ports
backup real-life work files, around 49.4GB, 41.000 files, 6.000 folders
External device BitLocker encrypted
used FreeFileSync app (high-quality freeware) that synchronizes directories as a backup solution The need for safe, offline backup is driven by ransomware attacks, which I actually experienced in my company. However, there are also other kinds of needs to move files between workstations, home, and office computers, and there is a need to have backup in case of system crashes or accidental deletions. safe, offline backup safe, offline backup For such situations External USB memory/disk devices are irreplaceable. I like them because I can attach them to make a backup and later detach them and physically move them to a safe place, where they are definitely offline. External USB memory/disk devices External USB memory/disk devices My favorite backup method is very simple one: the usage of FreeFileSync app (high-quality freeware) that synchronizes directories. I keep all my work files on my work laptop in one root folder and sync periodically to an External USB device. FreeFileSync app (high-quality freeware) FreeFileSync app (high-quality freeware) In compliance with company rules, I keep all my External USB devices BitLocker encrypted and secured with the password needed to access the device. There are many sensitive company and personal documents I have there, so I definitely want them safe in case memory/disk device is lost, for example during commuting to/from the office. BitLocker encrypted BitLocker encrypted Over the years technology for External USB memory/disk backup changed, bringing always greater transfer speeds. I bought some latest External SSD-s, so I wanted to test them. 2 Test scenario setup Here are the basic testing conditions: I will use a new Lenovo laptop with the newest USB A and USB C ports I will backup real life work files, around 49.4GB I will backup them to the External USB memory/disk device of choice External USB memory/disk device will be BitLocker encrypted I will use FreeFileSync app (high-quality freeware) that synchronizes directories as a backup solution I will use a new Lenovo laptop with the newest USB A and USB C ports newest USB A and USB C ports newest USB A and USB C ports I will backup real life work files, around 49.4GB real life work files, around 49.4GB real life work files, around 49.4GB I will backup them to the External USB memory/disk device of choice External USB memory/disk device will be BitLocker encrypted BitLocker encrypted BitLocker encrypted I will use FreeFileSync app (high-quality freeware) that synchronizes directories as a backup solution FreeFileSync app (high-quality freeware) FreeFileSync app (high-quality freeware) Here are the specs for the ports of my laptop: Here is the folder with real-life docs that I will backup: 3 Testing External 64GB USB Flash drive Device info: 64GB USB Flash drive Kinston DataTraveler 3.0 USB USB-A, 3.0 (5Gbps) 49.4GB transferred in 97min 15sec Average speed of backup 8.66MBps=69.26Mbps 64GB USB Flash drive Kinston DataTraveler 3.0 USB USB-A, 3.0 (5Gbps) 49.4GB transferred in 97min 15sec Average speed of backup 8.66MBps=69.26Mbps 4 Testing External 1 TB USB HDD Device info: External 1 TB USB HDD Toshiba 1 TB HDD USB-A, 3.0 (5Gbps) 49.4GB transferred in 22min 28sec Average speed of backup 37.5 MBps=300 Mbps External 1 TB USB HDD Toshiba 1 TB HDD USB-A, 3.0 (5Gbps) 49.4GB transferred in 22min 28sec Average speed of backup 37.5 MBps=300 Mbps 5 Testing External SSD 1 TB, USB 3.2 Gen2 Device info: External 1 TB SSD Samsung PSSD T7 1TB USB-C 3.2 Gen 2 (10Gbps) 49.4GB transferred in 4min 3sec Average speed of backup 208 MBps=1664 Mbps External 1 TB SSD Samsung PSSD T7 1TB USB-C 3.2 Gen 2 (10Gbps) 49.4GB transferred in 4min 3sec Average speed of backup 208 MBps=1664 Mbps 6 Testing External SSD 2 TB, USB 3.2 Gen2x2 Device info: External 2 TB SSD Samsung PSSD T9 2TB USB-C 3.2 Gen 2x2 (20Gbps) 49.4GB transferred in 2min 38sec Average speed of backup 320 MBps=2560 Mbps External 2 TB SSD Samsung PSSD T9 2TB USB-C 3.2 Gen 2x2 (20Gbps) 49.4GB transferred in 2min 38sec Average speed of backup 320 MBps=2560 Mbps 7 Conclusion So, here are actual practical speeds of backup in real-world situations: These values are measured in these conditions: used a new Lenovo laptop (December 2024) with the newest USB A and USB C ports backup real-life work files, around 49.4GB, 41.000 files, 6.000 folders External device BitLocker encrypted used FreeFileSync app (high-quality freeware) that synchronizes directories as a backup solution used a new Lenovo laptop (December 2024) with the newest USB A and USB C ports newest USB A and USB C ports newest USB A and USB C ports backup real-life work files, around 49.4GB, 41.000 files, 6.000 folders real-life work files, around 49.4GB, 41.000 files, 6.000 folders real-life work files, around 49.4GB, 41.000 files, 6.000 folders External device BitLocker encrypted BitLocker encrypted BitLocker encrypted used FreeFileSync app (high-quality freeware) that synchronizes directories as a backup solution FreeFileSync app (high-quality freeware) FreeFileSync app (high-quality freeware)

Samsung SSDs Have Become So Fast, They Make Competitors Look Like Floppy Disks

أصبحت أقراص SSD من سامسونج سريعة للغاية، لدرجة أنها تجعل المنافسين يبدون مثل الأقراص المرنة

SSD-назапашвальнікі Samsung сталі настолькі хуткімі, што яны робяць канкурэнтаў падобнымі на дыскеты

SSD дисковете на Samsung станаха толкова бързи, че карат конкурентите да изглеждат като флопи дискове

Los SSD de Samsung se han vuelto tan rápidos que hacen que sus competidores parezcan disquetes

SSD های سامسونگ بسیار سریع شده اند و رقبا را شبیه فلاپی دیسک می کنند

כונני SSD של סמסונג הפכו כל כך מהירים, שהם גורמים למתחרים להיראות כמו תקליטונים

सैमसंग के SSD इतने तेज़ हो गए हैं कि वे अपने प्रतिस्पर्धियों को फ्लॉपी डिस्क जैसा दिखाते हैं

サムスンのSSDはあまりにも高速になり、競合他社のSSDはフロッピーディスクのように見える

Samsung SSD ir kļuvuši tik ātri, ka tie liek konkurentiem izskatīties pēc disketēm

Samsung SSD-ууд маш хурдан болж, өрсөлдөгчдийг уян диск шиг харагдуулдаг

Samsung SSD-enheter har blivit så snabba att de får konkurrenter att se ut som disketter

Samsung SSDs Ti Humele Hi Ku hatlisa swinene, Ti Endla Leswaku Vaphikizani Va Languteka Ku fana Na Ti Floppy Disks

Hello Amazon aspirants!! I have recently cleared all interviews for the QAE II position at Amazon. I would like to share about the interview process, expectations, preparation tips and the resources I referred to during my preparation. Most of the information is already present on Web/YouTube. I am giving links to all resources here. Note: I am not giving any questions from my interview as I have signed disclosure not to share. About process Before jumping into preparation, first you need to understand the hiring process. After applying, I got a call from a recruiter. He explained me the process as below - Online Assessment — Link will be shared to us, and we will have around 1 week to finish that.
Phone Interview — This is 1 hour round, in which questions will be asked on 3 aspects: 1. Test cases ; 2. Coding; 3. Leadership Principles (Preparation is same as explained for Main interview)
Main Interview — 5 different rounds — 1 hr each (Total 5hrs). Here we have option to have all rounds on same day (there will be lunch break 1hr) OR we can divide them for 2 different days Below are those 5 rounds. Not necessarily in the same order. Online test: About testing process, behavioral and situation based questions. Objective type. 1. Coding 2. Test case Enumeration & Test data preparation 3. Test Planning / Strategy 4. Debugging round 5. Leadership Principles After completion of all the above interviews, the panel will meet and decide on your candidature. Within a week, the recruiter can provide you with feedback. Apart from this, go through the previous QA interview experiences from the Leetcode discussions section. *Important — One of the rounds in the process is “Leadership Principles”, where you will be asked certain situational based questions which you need to answer based on the examples in your experience. Similar leadership principles questions, 1–2 will be asked on other 4 rounds also. Around 30% of the other 4 rounds will be focussed on leadership principles questions and remaining 70% will be actual interviews about that round (Coding, Debugging, Testcases, TestPlanning). So, Leadership Principles questions are very important when you are preparing for an Amazon interview. Preparation: 1. Coding - First I started preparing for the Coding round. I got a Leetcode subscription. The difference with Leetcode subscription is, we will have more questions and we will have company tag names to the coding questions. I filtered all “Amazon” + “Easy” programs. In that, I have excluded questions related to Trees, graph related questions. Of the remaining challenges, I started solving them daily. Most of these challenges are based on Arrays, Strings, Collections. Initially, when I had no clue on the approach, I used to see the answer on the web and tried to understand(many YouTube videos are there for each question). In that way, I have improved and could solve new problems on my own. That way I did practice around 60 easy problems from Leetcode(There are around 200+ Amazon+Easy problems in Leetcode, related to Arrays, Strings, Collections). Apart from this, I have read past Amazon QAE interview experiences on Leetcode and different websites and collected some questions(around 15) and solved them too. In Total, I have solved around 75 problems. I repeated solving them 3–4 times. It doesn’t mean that we get interview questions from leetcode / previous questions. It only gives confidence to you to solve similar questions. I have focussed only on basic concepts — Arrays, Stings, Collections(HashMaps mostly) related programs. Also, refer this video - https://www.youtube.com/watch?v=cdeoqgEUSvE&embedable=true 2. Test case Enumeration & Test data preparation Here, you may be asked to list test cases for any given scenario. Do follow the video below for the tips on how to answer. These tips are very important. https://www.youtube.com/watch?v=Xz2oHPpz2hM&embedable=true Be prepared for 1–2 questions on leadership principles (mentioned on this topic at last) 3. Test Planning & Test Strategy Be prepared to write TestPlan / TestStrategy for any given scenario. You may be given any scenario, and will be asked to write / explain the test plan for it. Always, ask clarifying questions. https://www.guru99.com/how-to-create-test-strategy-document.html Be prepared for 1–2 questions on leadership principles (mentioned on this topic at last). 4. Debugging round In this round, you will be given an issue / bug and you will be asked to debug it. Basically, you need to explain the steps / checks you perform to isolate the issue. This video is helpful - https://www.youtube.com/watch?v=65_8WUtwDnE&embedable=true There are some sample questions here. Be prepared for 1–2 questions on leadership principles (mentioned on this topic at last). 5. Leadership Principles This is a very important area. Amazon has 14 leadership principles. You need to study and understand these principles. In the call with the recruiter, you will be informed if any of the 14 principles are not applicable to your role(QA). In my case, 2 are excluded. It means I need to prepare another 12 leadership principles. You will be given any situation based question and you need to answer it based on any related example in your past. Be prepared to explain it in detail with the background of the situation, what you did, how you did and results and learnings out of it. In many blogs and other experiences, it is recommended to have atleast 2 unique examples for each principle as the question may be repeated across the rounds and you should not repeat the same example/answer. Below is the great website, which helped me in understanding them, and know different types of questions based on each principle with sample answers. Take that as reference and build your own answers. https://interviewgenie.com/resources In the above page, go to this section - “The 16 Leadership Principles with Sample Questions and Answers That Get Results” That’s it for now! Please let me know if you have any doubts. Wish you all the best!! Hello Amazon aspirants!! I have recently cleared all interviews for the QAE II position at Amazon. I would like to share about the interview process, expectations, preparation tips and the resources I referred to during my preparation. Most of the information is already present on Web/YouTube. I am giving links to all resources here. Note: I am not giving any questions from my interview as I have signed disclosure not to share. About process About process Before jumping into preparation, first you need to understand the hiring process. After applying, I got a call from a recruiter. He explained me the process as below - Online Assessment — Link will be shared to us, and we will have around 1 week to finish that. Phone Interview — This is 1 hour round, in which questions will be asked on 3 aspects: 1. Test cases ; 2. Coding; 3. Leadership Principles (Preparation is same as explained for Main interview) Main Interview — 5 different rounds — 1 hr each (Total 5hrs). Here we have option to have all rounds on same day (there will be lunch break 1hr) OR we can divide them for 2 different days Online Assessment — Link will be shared to us, and we will have around 1 week to finish that. Phone Interview — This is 1 hour round, in which questions will be asked on 3 aspects: 1. Test cases ; 2. Coding; 3. Leadership Principles (Preparation is same as explained for Main interview) Main Interview — 5 different rounds — 1 hr each (Total 5hrs). Here we have option to have all rounds on same day (there will be lunch break 1hr) OR we can divide them for 2 different days Below are those 5 rounds. Not necessarily in the same order. Online test: Online test: About testing process, behavioral and situation based questions. Objective type. 1. Coding 1. Coding 2. Test case Enumeration & Test data preparation 2. Test case Enumeration & Test data preparation 3. Test Planning / Strategy 3. Test Planning / Strategy 4. Debugging round 4. Debugging round 5. Leadership Principles 5. Leadership Principles After completion of all the above interviews, the panel will meet and decide on your candidature. Within a week, the recruiter can provide you with feedback. Apart from this, go through the previous QA interview experiences from the Leetcode discussions section. *Important — One of the rounds in the process is “Leadership Principles”, where you will be asked certain situational based questions which you need to answer based on the examples in your experience. Similar leadership principles questions, 1–2 will be asked on other 4 rounds also. Around 30% of the other 4 rounds will be focussed on leadership principles questions and remaining 70% will be actual interviews about that round (Coding, Debugging, Testcases, TestPlanning). So, Leadership Principles questions are very important when you are preparing for an Amazon interview. So, Leadership Principles questions are very important when you are preparing for an Amazon interview. Preparation: Preparation: 1. Coding - 1. Coding - 1. Coding - First I started preparing for the Coding round. I got a Leetcode subscription. The difference with Leetcode subscription is, we will have more questions and we will have company tag names to the coding questions. I filtered all “Amazon” + “Easy” programs. In that, I have excluded questions related to Trees, graph related questions. Of the remaining challenges, I started solving them daily. Most of these challenges are based on Arrays, Strings, Collections. Initially, when I had no clue on the approach, I used to see the answer on the web and tried to understand(many YouTube videos are there for each question). In that way, I have improved and could solve new problems on my own. That way I did practice around 60 easy problems from Leetcode(There are around 200+ Amazon+Easy problems in Leetcode, related to Arrays, Strings, Collections). Apart from this, I have read past Amazon QAE interview experiences on Leetcode and different websites and collected some questions(around 15) and solved them too. In Total, I have solved around 75 problems. I repeated solving them 3–4 times. It doesn’t mean that we get interview questions from leetcode / previous questions. It only gives confidence to you to solve similar questions. I have focussed only on basic concepts — Arrays, Stings, Collections(HashMaps mostly) related programs. Also, refer this video - https://www.youtube.com/watch?v=cdeoqgEUSvE&embedable=true https://www.youtube.com/watch?v=cdeoqgEUSvE&embedable=true 2. Test case Enumeration & Test data preparation 2. Test case Enumeration & Test data preparation 2. Test case Enumeration & Test data preparation Here, you may be asked to list test cases for any given scenario. Do follow the video below for the tips on how to answer. These tips are very important. https://www.youtube.com/watch?v=Xz2oHPpz2hM&embedable=true https://www.youtube.com/watch?v=Xz2oHPpz2hM&embedable=true Be prepared for 1–2 questions on leadership principles (mentioned on this topic at last) 3. Test Planning & Test Strategy 3. Test Planning & Test Strategy 3. Test Planning & Test Strategy Be prepared to write TestPlan / TestStrategy for any given scenario. You may be given any scenario, and will be asked to write / explain the test plan for it. Always, ask clarifying questions. https://www.guru99.com/how-to-create-test-strategy-document.html https://www.guru99.com/how-to-create-test-strategy-document.html Be prepared for 1–2 questions on leadership principles (mentioned on this topic at last). 4. Debugging round 4. Debugging round 4. Debugging round In this round, you will be given an issue / bug and you will be asked to debug it. Basically, you need to explain the steps / checks you perform to isolate the issue. This video is helpful - https://www.youtube.com/watch?v=65_8WUtwDnE&embedable=true https://www.youtube.com/watch?v=65_8WUtwDnE&embedable=true There are some sample questions here . here Be prepared for 1–2 questions on leadership principles (mentioned on this topic at last). 5. Leadership Principles 5. Leadership Principles 5. Leadership Principles This is a very important area. Amazon has 14 leadership principles. 14 You need to study and understand these principles. In the call with the recruiter, you will be informed if any of the 14 principles are not applicable to your role(QA). In my case, 2 are excluded. It means I need to prepare another 12 leadership principles. You will be given any situation based question and you need to answer it based on any related example in your past. Be prepared to explain it in detail with the background of the situation, what you did, how you did and results and learnings out of it. In many blogs and other experiences, it is recommended to have atleast 2 unique examples for each principle as the question may be repeated across the rounds and you should not repeat the same example/answer. Below is the great website, which helped me in understanding them, and know different types of questions based on each principle with sample answers. Take that as reference and build your own answers. https://interviewgenie.com/resources https://interviewgenie.com/resources In the above page, go to this section - “The 16 Leadership Principles with Sample Questions and Answers That Get Results” “The 16 Leadership Principles with Sample Questions and Answers That Get Results” That’s it for now! Please let me know if you have any doubts. Wish you all the best!!

How I Cracked the Amazon QAE II Interview

Introduction If you’re a Mac user and have ever wanted to run a Python script automatically at a specific time, MacOS has a built-in tool called crontab that lets you schedule tasks to run at specified intervals. This article will guide you through the steps to set up and use crontab to schedule your Python scripts. Step 1: Edit the Crontab File To edit the crontab file, run the following command in Terminal: crontab -e Step 2: Schedule Your Python Script In the crontab file, you’ll need to add a new line that specifies when and how often your script should run. The basic syntax for a crontab entry is: * * * * * /path/to/python /path/to/your/script.py Here’s what each * represents (from left to right): Minute (0-59)
Hour (0-23)
Day of the month (1-31)
Month (1-12)
Day of the week (0-7, where 0 and 7 represent Sunday) For example, if you want your script to run every day at 7:30 AM, you would write: 30 7 * * * /usr/bin/python3 /Users/yourusername/example.py Replace /usr/bin/python3 with the actual path to your Python interpreter from running which python3 in Terminal and /Users/yourusername/example.py with the path to your script. It’s important to note that the paths don’t need to be enclosed in quotation marks. Step 3: Save and Exit After you’ve added the line to schedule your script, save the file and exit the editor. If you’re using the default editor, you can save your changes by pressing Ctrl + O, then hit Enter to confirm. Finally, press Ctrl + X to exit the editor. Verifying Your Crontab Setup If you’re new to crontab, a simple way to check if it’s working correctly is by creating a Python script that logs the current time every time it runs. Here’s how you can do it: Step 1: Create a Simple Python Script Create a script called log_test.py that writes the current date and time to a log file: import datetime

# Define the log file path
log_file_path = "/path/to/your/log_file.txt"

# Get the current time
current_time = datetime.datetime.now()

# Write the current time to the log file
with open(log_file_path, "a") as log_file:
    log_file.write(f"Script ran at: {current_time}\n") Replace "/path/to/your/log_file.txt" with the path where you want the log file to be saved. Step 2:  Test Your Script in the Terminal Before scheduling the script with crontab, it’s important to ensure that it runs correctly in the terminal. Open the Terminal and execute the following command: /usr/bin/python3 /path/to/your/log_test.py Replace /usr/bin/python3 with the path to your Python interpreter and /path/to/your/log_test.py with the path to your script. If the command runs without errors and you see a new entry in your log file, your script is ready to be scheduled. Step 3: Update and Save Your Crontab To schedule the script to run every minute, add this line to your crontab: * * * * * /usr/bin/python3 /path/to/your/log_test.py Replace /usr/bin/python3 and /path/to/your/log_test.py with the correct paths on your system. Step 4: Check the Log File After a few minutes, check the log file. If you see new timestamps, your crontab job is working! Conclusion Congratulations! You’ve now set up a Python script to run automatically on your Mac using crontab. This is a powerful way to automate tasks, from running backups to generating reports. With crontab, you can ensure your Python scripts run exactly when you need them to, without any manual intervention. Thank you for taking the time to explore data-related insights with me. I appreciate your engagement. If you find this information helpful, I invite you to follow me or connect with me on LinkedIn. Happy exploring!👋 Introduction If you’re a Mac user and have ever wanted to run a Python script automatically at a specific time, MacOS has a built-in tool called crontab that lets you schedule tasks to run at specified intervals. This article will guide you through the steps to set up and use crontab to schedule your Python scripts. crontab Step 1: Edit the Crontab File To edit the crontab file, run the following command in Terminal: crontab -e crontab -e Step 2: Schedule Your Python Script In the crontab file, you’ll need to add a new line that specifies when and how often your script should run. The basic syntax for a crontab entry is: * * * * * /path/to/python /path/to/your/script.py * * * * * /path/to/python /path/to/your/script.py Here’s what each * represents (from left to right): Minute (0-59) Hour (0-23) Day of the month (1-31) Month (1-12) Day of the week (0-7, where 0 and 7 represent Sunday) Minute (0-59) Minute Hour (0-23) Hour Day of the month (1-31) Day of the month Month (1-12) Month Day of the week (0-7, where 0 and 7 represent Sunday) Day of the week For example, if you want your script to run every day at 7:30 AM, you would write: 30 7 * * * /usr/bin/python3 /Users/yourusername/example.py 30 7 * * * /usr/bin/python3 /Users/yourusername/example.py Replace /usr/bin/python3 with the actual path to your Python interpreter from running which python3 in Terminal and /Users/yourusername/example.py with the path to your script. /usr/bin/python3 which python3 /Users/yourusername/example.py It’s important to note that the paths don’t need to be enclosed in quotation marks. Step 3: Save and Exit After you’ve added the line to schedule your script, save the file and exit the editor. If you’re using the default editor, you can save your changes by pressing Ctrl + O , then hit Enter to confirm. Finally, press Ctrl + X to exit the editor. Ctrl + O Enter Ctrl + X Verifying Your Crontab Setup If you’re new to crontab, a simple way to check if it’s working correctly is by creating a Python script that logs the current time every time it runs. Here’s how you can do it: Step 1: Create a Simple Python Script Create a script called log_test.py that writes the current date and time to a log file: log_test.py import datetime

# Define the log file path
log_file_path = "/path/to/your/log_file.txt"

# Get the current time
current_time = datetime.datetime.now()

# Write the current time to the log file
with open(log_file_path, "a") as log_file:
    log_file.write(f"Script ran at: {current_time}\n") import datetime

# Define the log file path
log_file_path = "/path/to/your/log_file.txt"

# Get the current time
current_time = datetime.datetime.now()

# Write the current time to the log file
with open(log_file_path, "a") as log_file:
    log_file.write(f"Script ran at: {current_time}\n") Replace "/path/to/your/log_file.txt" with the path where you want the log file to be saved. Step 2:  Test Your Script in the Terminal Before scheduling the script with crontab, it’s important to ensure that it runs correctly in the terminal. Open the Terminal and execute the following command: /usr/bin/python3 /path/to/your/log_test.py /usr/bin/python3 /path/to/your/log_test.py Replace /usr/bin/python3 with the path to your Python interpreter and /path/to/your/log_test.py with the path to your script. If the command runs without errors and you see a new entry in your log file, your script is ready to be scheduled. Step 3: Update and Save Your Crontab To schedule the script to run every minute, add this line to your crontab: * * * * * /usr/bin/python3 /path/to/your/log_test.py * * * * * /usr/bin/python3 /path/to/your/log_test.py Replace /usr/bin/python3 and /path/to/your/log_test.py with the correct paths on your system. Step 4: Check the Log File After a few minutes, check the log file. If you see new timestamps, your crontab job is working! Conclusion Congratulations! You’ve now set up a Python script to run automatically on your Mac using crontab. This is a powerful way to automate tasks, from running backups to generating reports. With crontab, you can ensure your Python scripts run exactly when you need them to, without any manual intervention. Thank you for taking the time to explore data-related insights with me. I appreciate your engagement. If you find this information helpful, I invite you to follow me or connect with me on LinkedIn . Happy exploring!👋 LinkedIn

Automate Python Scripts on Mac: A Step-by-Step Guide to Scheduling with Crontab

Isha Varshney with Rosette Belesi, Product Marketing Director at Opera, at OpenFi discussing "Building, Scaling & Enhancing MiniPay to Onboard African Users to Web3." Photo by Benjamin Arthur, courtesy of IdOS. During EthCC, I had a chance to catch up with Isha Varshney, Head of Ecosystem at the Celo Foundation, who has extensive experience in decentralized finance and global financial inclusion initiatives. Given the main criticism around EthCC that “there are more side events than dApps,” we focused our conversation on building for the real world and MiniPay, a Celo-based app that has seen significant success in Africa with over 3 million wallet activations across Nigeria, Ghana, Kenya, and South Africa. Isha, how are you enjoying EthCC? Any key themes you’re noticing? EthCC has been incredible. Some of the major themes revolve around Layer 2 solutions. Last Sunday, core contributors cLabs launched the Celo Layer 2testnet, Dango. It's exciting to see the momentum as Celo migrates to join the OP Stack, a modular blockchain architecture. We also participated in several events with Superchain and the OP Stack team, bringing together incredible builders. It's thrilling to see so many talented teams and individuals joining this ecosystem. What are the biggest challenges in bringing Web3 to the mainstream? Is there still a big gap? Yes and no. We're still in the early stages of Web3 and crypto. Much of the technology is highly technical and not immediately relevant to the everyday person—like my mom or friends who might not understand concepts like intents. However, these building blocks are crucial for the technology's development and interoperability. The work we're doing now is laying the foundation for the future. In about five years, we hope to abstract crypto away from everyday users, making it seamlessly integrated into their lives. We're at an exciting juncture where we're building the infrastructure that will soon bring Web3 to the mainstream. Building for users’ current needs and behaviors is a crucial component of this—and that means building for mobile devices. With roughly ¾ of the world’s population owning smartphones, far more than the population that has access to a computer, and financial activity increasingly being conducted by mobile devices, it’s necessary that we build mobile-first. This is what excites me about so many projects in the Celo ecosystem that are developing solutions to everyday challenges that users can incorporate into their daily lives. What are the key elements needed to build the next great decentralized application (dApp)? We're not thinking enough about everyday usability in this space. Interacting with crypto can be complicated and intimidating. For example, using most crypto wallets involves signing transactions and dealing with private keys, public keys, and wallet addresses, which are not exactly user-friendly. One solution to address this is SocialConnect, a primitive developed for Celo that allows users to leverage their phone numbers as their wallet addresses. This kind of simplicity is crucial. We need more technology like that to onboard the next billion users. For crypto and Web3 to go mainstream, it has to be easy and intuitive for users. When you talk to people who aren't in Web3, they often find it speculative and scary. What we need next is to remove these frictions and make it easy to understand. We're working on it and making progress in this space. MiniPay has seen amazing growth. Can you share its journey and what it does? The collaboration between Celo and Opera is fascinating. Opera, a browser with 100 million users across Africa, is pre-installed on every Android device. In Africa, Android devices are ubiquitous, and people primarily interact with technology through their phones. Opera initially gained popularity by providing some free data, which is costly in many African regions, enabling anyone to browse the internet for one or two hours daily, opening up access for many users. Celo’s ecosystem has always focused on real-world applications in these markets, so partnering with Opera was a natural fit. With their extensive distribution network, we integrated a wallet into the existing mobile Android browser used by millions, making it simple and accessible. We launched this wallet in September last year, rolling it out country by country. Starting in Nigeria, we now operate in Kenya, Ghana, Nigeria, and South Africa. We now have over 3 million users, onboarding a massive number of new users daily. The wallet is designed with a stablecoin-only interface and a user-friendly UI/UX, allowing users to sign in with their Google account, making it incredibly easy to use. Why is the stablecoin aspect important? Are stablecoins the perfect gateway to Web3? Absolutely. Stablecoins are vital because they offer a consistent value in contrast to the often volatile nature of other cryptocurrencies. In emerging economies, where local currencies can be deflationary, people are familiar with and trust the value of the US dollar. Stablecoins provide this reliability, making them an ideal entry point into Web3. They give users confidence that their money will hold its value, which is crucial in markets where per-wallet volumes aren't large and financial security is paramount. We started with the Celo Dollar (cUSD) in the wallet and recently expanded to include USDC from Circle and Tether’s USDT. The wallet's Pockets feature displays USDC, USDT, and cUSD in a simple, clean interface. Users can easily swap between these stablecoins by dragging and swapping from asset to asset—one of the only 1:1 stablecoin swap features on the market. The ease of use enhances accessibility while also bringing the experience of transacting with multiple stables to users who might be unfamiliar. What advice do you have for builders trying to create for the people? My experience with the Opera team has been incredible. They execute like no other team. They have over 1,000 ambassadors on the ground across all these markets and are constantly engaging with their ambassador network. This network helps onboard and troubleshoot with users, ensuring a smooth experience. Opera takes feedback and builds on it really well. For example, we started with only cUSD, and the feedback was that users were familiar with other stablecoins and wanted to be able to use them in MiniPay. So, we added those to the product, meeting users where they are. That's my message to builders: meet people where they are. If they're familiar with something, leverage that. It's already challenging enough, so let's not reinvent the wheel. With Celo, from day one, we've built for real-world use cases. Every step of the way, we've focused on building for practical applications, like microcredit in emerging markets with EthicHub or Haraka. We're committed to meeting users where they are and will continue to do so with MiniPay and all other projects. What’s one app you’d really like to see built next? Hmm, that’s a good one! I would love to see an all-in-one app similar to WeChat in China, which covers everything from payments to utilities. MiniPay is moving towards that vision for Africa with the inclusion of a Discover Page for the growing roster of integrated dApps. Imagine a single platform where you can handle all your needs using stablecoins or a corporate-backed currency. For instance, as frequent travelers, we constantly switch SIM cards. What if we could abstract that concept, not just for SIM cards but for all forms of payment? It would be fantastic to have a seamless payment experience, no matter where you are. If I’m in Brussels and from New York, I should be able to pay for everything with the same app. It would make managing finances and daily activities so much simpler and more convenient. Isha Varshney with Rosette Belesi, Product Marketing Director at Opera, at OpenFi discussing "Building, Scaling & Enhancing MiniPay to Onboard African Users to Web3." Photo by Benjamin Arthur, courtesy of IdOS. Isha Varshney with Rosette Belesi, Product Marketing Director at Opera, at OpenFi discussing "Building, Scaling & Enhancing MiniPay to Onboard African Users to Web3." Photo by Benjamin Arthur , courtesy of IdOS. Benjamin Arthur During EthCC, I had a chance to catch up with Isha Varshney, Head of Ecosystem at the Celo Foundation, who has extensive experience in decentralized finance and global financial inclusion initiatives. Given the main criticism around EthCC that “there are more side events than dApps,” we focused our conversation on building for the real world and MiniPay, a Celo-based app that has seen significant success in Africa with over 3 million wallet activations across Nigeria, Ghana, Kenya, and South Africa. During EthCC, I had a chance to catch up with Isha Varshney, Head of Ecosystem at the Celo Foundation, who has extensive experience in decentralized finance and global financial inclusion initiatives. Given the main criticism around EthCC that “there are more side events than dApps,” we focused our conversation on building for the real world and MiniPay, a Celo-based app that has seen significant success in Africa with over 3 million wallet activations across Nigeria, Ghana, Kenya, and South Africa. During EthCC, I had a chance to catch up with Isha Varshney , Head of Ecosystem at the Celo Foundation , who has extensive experience in decentralized finance and global financial inclusion initiatives. Given the main criticism around EthCC that “there are more side events than dApps,” we focused our conversation on building for the real world and MiniPay , a Celo-based app that has seen significant success in Africa with over 3 million wallet activations across Nigeria, Ghana, Kenya, and South Africa. Isha Varshney Isha Varshney Celo Foundation Celo Foundation MiniPay MiniPay over 3 million wallet activations over 3 million wallet activations Isha, how are you enjoying EthCC? Any key themes you’re noticing? Isha, how are you enjoying EthCC? Any key themes you’re noticing? EthCC has been incredible. Some of the major themes revolve around Layer 2 solutions. Last Sunday, core contributors cLabs launched the Celo Layer 2testnet, Dango. It's exciting to see the momentum as Celo migrates to join the OP Stack, a modular blockchain architecture. We also participated in several events with Superchain and the OP Stack team, bringing together incredible builders. It's thrilling to see so many talented teams and individuals joining this ecosystem. What are the biggest challenges in bringing Web3 to the mainstream? Is there still a big gap? Yes and no. We're still in the early stages of Web3 and crypto. Much of the technology is highly technical and not immediately relevant to the everyday person—like my mom or friends who might not understand concepts like intents. However, these building blocks are crucial for the technology's development and interoperability. The work we're doing now is laying the foundation for the future. In about five years, we hope to abstract crypto away from everyday users, making it seamlessly integrated into their lives. We're at an exciting juncture where we're building the infrastructure that will soon bring Web3 to the mainstream. Building for users’ current needs and behaviors is a crucial component of this—and that means building for mobile devices. With roughly ¾ of the world’s population owning smartphones, far more than the population that has access to a computer, and financial activity increasingly being conducted by mobile devices, it’s necessary that we build mobile-first. This is what excites me about so many projects in the Celo ecosystem that are developing solutions to everyday challenges that users can incorporate into their daily lives. What are the key elements needed to build the next great decentralized application (dApp)? We're not thinking enough about everyday usability in this space. Interacting with crypto can be complicated and intimidating. For example, using most crypto wallets involves signing transactions and dealing with private keys, public keys, and wallet addresses, which are not exactly user-friendly. One solution to address this is SocialConnect, a primitive developed for Celo that allows users to leverage their phone numbers as their wallet addresses. This kind of simplicity is crucial. We need more technology like that to onboard the next billion users. For crypto and Web3 to go mainstream, it has to be easy and intuitive for users. When you talk to people who aren't in Web3, they often find it speculative and scary. What we need next is to remove these frictions and make it easy to understand. We're working on it and making progress in this space. MiniPay has seen amazing growth. Can you share its journey and what it does? The collaboration between Celo and Opera is fascinating. Opera, a browser with 100 million users across Africa, is pre-installed on every Android device. In Africa, Android devices are ubiquitous, and people primarily interact with technology through their phones. Opera initially gained popularity by providing some free data, which is costly in many African regions, enabling anyone to browse the internet for one or two hours daily, opening up access for many users. Celo’s ecosystem has always focused on real-world applications in these markets, so partnering with Opera was a natural fit. With their extensive distribution network, we integrated a wallet into the existing mobile Android browser used by millions, making it simple and accessible. We launched this wallet in September last year, rolling it out country by country. Starting in Nigeria, we now operate in Kenya, Ghana, Nigeria, and South Africa. We now have over 3 million users, onboarding a massive number of new users daily. The wallet is designed with a stablecoin-only interface and a user-friendly UI/UX, allowing users to sign in with their Google account, making it incredibly easy to use. Why is the stablecoin aspect important? Are stablecoins the perfect gateway to Web3? Absolutely. Stablecoins are vital because they offer a consistent value in contrast to the often volatile nature of other cryptocurrencies. In emerging economies, where local currencies can be deflationary, people are familiar with and trust the value of the US dollar. Stablecoins provide this reliability, making them an ideal entry point into Web3. They give users confidence that their money will hold its value, which is crucial in markets where per-wallet volumes aren't large and financial security is paramount. We started with the Celo Dollar (cUSD) in the wallet and recently expanded to include USDC from Circle and Tether’s USDT. The wallet's Pockets feature displays USDC, USDT, and cUSD in a simple, clean interface. Users can easily swap between these stablecoins by dragging and swapping from asset to asset—one of the only 1:1 stablecoin swap features on the market. The ease of use enhances accessibility while also bringing the experience of transacting with multiple stables to users who might be unfamiliar. Pockets feature Pockets feature What advice do you have for builders trying to create for the people? My experience with the Opera team has been incredible. They execute like no other team. They have over 1,000 ambassadors on the ground across all these markets and are constantly engaging with their ambassador network. This network helps onboard and troubleshoot with users, ensuring a smooth experience. Opera takes feedback and builds on it really well. For example, we started with only cUSD, and the feedback was that users were familiar with other stablecoins and wanted to be able to use them in MiniPay. So, we added those to the product, meeting users where they are. That's my message to builders: meet people where they are. If they're familiar with something, leverage that. It's already challenging enough, so let's not reinvent the wheel. With Celo, from day one, we've built for real-world use cases. Every step of the way, we've focused on building for practical applications, like microcredit in emerging markets with EthicHub or Haraka . We're committed to meeting users where they are and will continue to do so with MiniPay and all other projects. EthicHub EthicHub Haraka Haraka What’s one app you’d really like to see built next? Hmm, that’s a good one! I would love to see an all-in-one app similar to WeChat in China, which covers everything from payments to utilities. MiniPay is moving towards that vision for Africa with the inclusion of a Discover Page for the growing roster of integrated dApps. Imagine a single platform where you can handle all your needs using stablecoins or a corporate-backed currency. For instance, as frequent travelers, we constantly switch SIM cards. What if we could abstract that concept, not just for SIM cards but for all forms of payment? It would be fantastic to have a seamless payment experience, no matter where you are. If I’m in Brussels and from New York, I should be able to pay for everything with the same app. It would make managing finances and daily activities so much simpler and more convenient.

Successful dApps Make Web3 Invisible to Users, Says Celo’s Isha Varshney

সফল dApps Web3 ব্যবহারকারীদের কাছে অদৃশ্য করে তোলে, সেলোর ইশা ভার্শনি বলেছেন

Erfolgreiche dApps machen Web3 für Benutzer unsichtbar, sagt Isha Varshney von Celo

Las dApps exitosas hacen que Web3 sea invisible para los usuarios, dice Isha Varshney de Celo

Les dApps réussies rendent le Web3 invisible pour les utilisateurs, déclare Isha Varshney de Celo

सेलो की ईशा वार्ष्णेय का कहना है कि सफल dApps वेब3 को उपयोगकर्ताओं के लिए अदृश्य बना देते हैं

CeloのIsha Varshney氏は、成功したdAppsはWeb3をユーザーから見えなくする、と語る

Celo의 Isha Varshney는 성공적인 dApp으로 인해 Web3가 사용자에게 보이지 않게 된다고 말합니다.

DApps bem-sucedidos tornam a Web3 invisível para os usuários, afirma Isha Varshney da Celo

Успешные dApps делают Web3 невидимым для пользователей, говорит Иша Варшни из Celo

Celo'dan Isha Varshney, Başarılı dApp'lerin Web3'ü Kullanıcılara Görünmez Hale Getirdiğini Söyledi

Isha Varshney của Celo cho biết các dApp thành công khiến Web3 trở nên vô hình đối với người dùng

Celo 的 Isha Varshney 表示，成功的 dApp 让 Web3 对用户来说变得不可见

Deep Neural Networks to Detect and Quantify Lymphoma Lesions: Results

ডিপ নিউরাল নেটওয়ার্ক লিম্ফোমা ক্ষত সনাক্ত এবং পরিমাপ করতে: ফলাফল

Tiefe neuronale Netzwerke zur Erkennung und Quantifizierung von Lymphomläsionen: Ergebnisse

Redes neuronales profundas para detectar y cuantificar lesiones de linfoma: resultados

Réseaux de neurones profonds pour détecter et quantifier les lésions de lymphome : résultats

लिम्फोमा घावों का पता लगाने और मात्रा निर्धारित करने के लिए डीप न्यूरल नेटवर्क: परिणाम

リンパ腫病変を検出し定量化するディープニューラルネットワーク：結果

림프종 병변을 탐지하고 정량화하기 위한 심층 신경망: 결과

Redes Neurais Profundas para Detectar e Quantificar Lesões de Linfoma: Resultados

Глубокие нейронные сети для обнаружения и количественной оценки поражений лимфомой: результаты

Lenfoma Lezyonlarını Tespit Etmek ve Ölçmek İçin Derin Sinir Ağları: Sonuçlar

Mạng lưới thần kinh sâu để phát hiện và định lượng tổn thương ung thư hạch: Kết quả

深度神经网络检测和量化淋巴瘤病变：结果

Stories, News & Mentions about 2TEST

2test’s Stories on HackerNoon

2test's News & Mentions