开源日报 - Page 25 of 262 - Open Source Daily

开源日报第942期：《头像生成 avatar-generator》

7 11 月, 2020
开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《头像生成 avatar-generator》
今日推荐英文原文：《What if the Customer Can’t Reproduce Your Bug?》

今日推荐开源项目：《头像生成 avatar-generator》传送门：项目链接
推荐理由：这个项目可以让你根据需要快速定制一个卡通人头像用在各种社交媒体等地方作为账户头像，允许用户调整诸如嘴型与鼻子等这样的面部细节以及肤色等，如果觉得麻烦也可以使用全部随机来让运气决定会得出什么搭配来。
今日推荐英文原文：《What if the Customer Can’t Reproduce Your Bug?》作者：Sandra Parker
原文链接：https://medium.com/better-programming/what-if-the-customer-cant-reproduce-your-bug-7ddb2b1dc276
推荐理由：在其他人无法重现可能存在的 bug 时寻找原因的方法
What if the Customer Can’t Reproduce Your Bug?

“What are we doing wrong?”
Software quality assurance and testing are complicated procedures that require dedication, technical expertise, an eye for detail, and hours of work. Testers are people who dive deep into your product and have a major impact on the final project’s outcomes. That’s why it is so important that the product owners understand well not only the importance of software testing but its pain points from within for more effective communication.

Today’s article focuses on bug reproduction issues that usually remain behind the scenes for everyone but testers, which isn’t always good for the whole software project’s quality.
“Can’t Reproduce” — What Are We Doing Wrong?
Many software testers sooner or later face a problem where a customer/their team can’t reproduce a reported bug. A bug that you spent time and effort investigating. You tried so hard to report it back in a clear and concise manner, and yet they throw the “can’t reproduce” verdict in your face.

Trouble communicating is the top reason why anyone on the team fails to reproduce a bug. Either a vague bug summary was provided or it was a great one that no one wants to read.

Someone might experience troubles reproducing a bug because of a tester’s actions as well. For example, they might have provided a vague bug summary, listed uncertain steps to reproduce it, or enclosed a useless attachment that either doesn’t demonstrate the bug correctly or doesn’t want to open at all. It’s even worse if you didn’t check the bug reproduction before getting to the report and it stopped reproducing after the cache was cleared.

In case you are sure that the bug was reported correctly and can be found by the application end users, you have no other choice but to defend it. This is achieved through communication with all stakeholders who can investigate and fix that bug in the future.
Questions You Should Ask Your QA Team to Find Out Why They Can’t Reproduce Your Bug
- Do you use the same testing environments (platform, browser, browser version, device, OS, screen resolution)?
- What type of internet connection did you and the testing team use?
- Has the team accounted for all the preconditions and steps for bug reproduction that you specified?
- Does your expected result of software behavior match those of the team as well as the expected testing outcomes stated in the project requirements?
- Do you or your team use any third-party apps or browser extensions that could affect the software’s performance?
Let’s Look at All These Questions in More Detail
First of all, in most cases, the team doesn’t finish reading your bug. In the best-case scenario, a person trying to reproduce your bug has read more than the bug summary and its attachment. That’s why it is no wonder some of the bug report attributes often get missed. Yes, it is as unfortunate as it sounds.
Do your testing environments match?
You have to specify which exact environment the team checked your bug in.

It is assumed that the environment of a reproducing bug was stated in the description of it. Therefore, you have to double-check whether your colleague who’s trying to reproduce the bug is using the same platform to do it (browser, device, operating system, screen resolution) as you did.

As an example, we once had a case where our tester reported a bug that could only be reproduced on iPhone 6 but no other versions. That’s why they specified the particular environment in the bug report description. A developer who had to process that bug report didn’t pay attention to the fact that the bug can only be seen on a specified device. Since they only had an iPhone 7 on hand, they couldn’t reproduce the reported issue. Only after we double-checked everything was the misunderstanding finally solved. The bug that used to occur on iPhone 6 exclusively was found and fixed.
What type of internet connection did you and the testing team use?
For the most part, such a question should be asked about device-associated bugs because the type of internet connection (wifi, 3G, 4G, etc.) can affect the performance of an application or site, so this information is really important and has to be clarified.

Although, it turned out this issue is not only relevant for mobile. On one of our projects, we found an interesting bug: The online store did not display a map of post offices available for certain delivery methods. We discovered it when everyone was working from home due to the quarantine. The customer team could not reproduce the bug. For them, it seemed as if everything was perfectly displayed. After a few discussions, we decided to put the bug under investigation. After a part of our team got back to the office, we found that the bug could no longer be reproduced.

Since some of the employees continued working remotely, we managed to discover a fascinating fact. With a home internet connection, the bug kept reproducing. Meanwhile, in our office, where the connection was more stable, the post office map was displayed successfully — just like on the customer’s side. That’s when we decided to include the information on the internet connection type and its speed in the bug report.

As you can see, the internet connection itself can be a reason for a bug. In our case, it led to certain customers being unable to place their orders in that online store.
Has the team accounted for all the preconditions and steps for bug reproduction that you specified?
Getting back to the issue of the team not paying enough attention to the bug summary and its attachment, sometimes the team misses some important information — namely how to reproduce a particular bug.

Frequently, qualified employees tend to think they have mastered a project’s functionality to the point where they don’t need to examine the steps to reproduce the bug and its preconditions thoroughly. That’s why it’s worth double-checking how exactly developers tried to reproduce your bug and whether they missed a step or didn’t take into account any preconditions.

We had a case where a bug was reproducing only after we marked one out of four checkboxes for one country in the settings of software under testing. We added all this information to the bug description, which our colleague didn’t finish reading, and as a result, they could not reproduce the bug since they were following the usual steps to reproduce one.
Does your expected result of software behavior match those of the team as well as the expected testing outcomes stated in the project requirements?
It happens. You reported a bug because it didn’t match the expected result specified in the requirements or even ones that weren’t specified, but you know exactly how the functionality should perform based on your experience, general standards, or just common sense. You should discuss this issue with your colleagues. Maybe someone on the team is relying on inaccurate information about the expected result of the software behavior. Do you or your team use any third-party apps or browser extensions that could affect the software’s performance?

And the last question to discuss is the one that could be asked by the bug report author. Sometimes, certain apps can conflict with each other. Naturally, this provokes software errors that QA analysts classify as bugs. Even VPNs can affect the work. Therefore, you have to make sure during the bug reproduction that there are no third-party applications installed that are able to affect the performance of the tested product and mislead the entire team. For example, you’re using a virtual machine for testing that can be less stable than the original platform or a browser itself. This also has to be clarified.

Our colleague once reported a bug displaying unnecessary web elements on a page. No one else on the team could reproduce that bug. As it was later revealed, the bug author used a spelling assistant application that was reacting to certain web elements.
Wrapping Up
The aim of a software tester is to assure stable and error-free software functionality and prevent users from spotting bugs. That’s why we examine and classify all the bugs you may ever encounter. We take full responsibility for the quality of a tested product, a high-quality bug report if necessary, and the high-quality processing of it.

If you find a bug that seems like a serious reason to cancel the product release and the team cannot reproduce it, you should definitely find out the reasons why by asking the questions listed above. This will not only shape your professional reputation but also affect the image of the entire QA department in the eyes of the development team. A company’s position in front of its end users is a fragile thing that is so hard to get yet so easy to lose through a single serious mistake.
下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报第941期：《移动安全框架 MobSF》

6 11 月, 2020

开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《移动安全框架 MobSF》
今日推荐英文原文：《Biden moves closer to victory》

今日推荐开源项目：《移动安全框架 MobSF》传送门：项目链接
推荐理由：MobSF（Mobile Security Framework）是一个移动端应用安全问题检出的框架和工具，它适用于Android/iOS/Windows，能够执行动态和静态的恶意软件的分析和检测。支持Android和iOS以及Windows移动应用，无论是二进制方式还是压缩的源代码都可以进行检测。上传应用即可获得整体结果。
今日推荐英文原文：《Biden moves closer to victory》作者：AI HEPING
原文链接：https://www.chinadaily.com.cn/a/202011/05/WS5fa3a541a31024ad0ba8352b.html
推荐理由：2020年美国大选于当地时间11月3日开始，如今结果即将出炉。截止至笔者转载该文章时，拜登以264张选举人票暂时领先特朗普的214张，而在剩下的州里，内华达州的投票结果或许决定着美国大选的走向。但是特朗普团队相继起诉了3个州，要求它们暂停计票，并宣布要求威斯康星州重新计票，结果尚不明朗。
Biden moves closer to victory

Democratic presidential nominee Joe Biden takes his face mask off as he arrives to speak one day after Americans voted in the presidential election in Wilmington, Delaware on Nov 4, 2020. [Photo/Agencies]
Former Democratic vice-president Joe Biden on Wednesday won the key battleground states of Michigan and Wisconsin with razor-thin margins and was closing in on winning the Electoral College and the US presidency.

Winning the two states gave Biden 264 electoral votes, according to The Associated Press. It said if he wins any of four remaining states where vote counts continue — Nevada, Pennsylvania, Georgia and North Carolina — the 77-year-old Biden would be president-elect.

President Donald Trump on Wednesday filed lawsuits in Pennsylvania, Georgia and North Carolina as he fell behind Biden in seeking the 270 Electoral College votes needed to win the White House.

In Pennsylvania, nearly 1.1 million mail ballots remained uncounted by early Wednesday evening, including more than 167,000 in Philadelphia and nearly 156,000 in Allegheny County, where Pittsburgh is located, traditionally Democratic areas.

In Nevada, 86 percent of estimated votes have been reported, and state election authorities aren’t planning to release another update until Thursday.

In the popular vote, Biden had about 71 million votes to Trump’s 68 million.

In 2016, Trump won the Electoral College 306 to 232 for Hillary Clinton, who won the popular vote — 65.84 million votes to 62.98 million for Trump.

Republicans appeared to maintain narrow control of the US Senate and reduced the size of the Democrats’ majority in the House of Representatives.

In the race for the Senate, Democrats were still two or three seats short they would need to take control of the chamber. In Georgia, one race was headed for a January runoff, and Democrats were hopeful another race would face a runoff.

The AP’s projection on early Wednesday of Biden winning Arizona narrowed what it said was his road to winning the presidency. But unlike AP, some media organizations didn’t project Biden the winner in the swing state that Trump won in 2016.

Heading into Tuesday’s election, polls had shown Trump trailing Biden significantly, but the president’s conservative base of supporters turned out in big numbers on Election Day, leading to the close races in key battleground states.

Americans woke up on Wednesday to uncertainty over results in several states, with Trump and Biden both claiming that they would emerge victorious.

On Wednesday, Trump turned to the Supreme Court to intervene in voting in Pennsylvania and demanded a recount in Wisconsin.

His campaign filed a request with the high court to intervene and overturn a Pennsylvania state Supreme Court ruling allowing election officials to count mail-in ballots received up to three days after the election.

The Biden campaign said it was confident that he would win Pennsylvania because a majority of the uncounted ballots were from heavily Democratic areas.

Democratic Governor Tom Wolf said the state will continue to count ballots.

Despite fears that the election was so contentious it could spark civil unrest on Election Day, there were few reports of violence in cities, where many stores had boarded-up windows, but there was no certainty to that as the outcome remains in doubt.

In addition to winning Ohio and Florida, as he did in 2016, the president took Texas, which had emerged as a battleground for the first time in decades. Trump made gains among Hispanic voters, a crucial voting bloc for Democrats, in some states, but especially in Florida.

Speaking from the White House early on Wednesday, Trump prematurely claimed he had won the election and threatened to go to the Supreme Court to stop votes being counted.

He claimed without proof that counting votes after Election Day was a “major fraud”. “It’s a very sad moment,” he said at the White House. “We will win this, and as far as I am concerned, we already have.”

Biden accused Trump of making an “outrageous” statement that was a “naked effort to take away the democratic rights of American citizens”.

下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报第940期：《base-admin》

5 11 月, 2020

开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《base-admin》
今日推荐英文原文：《On Election Day, Twitter battles voting misinformation》

今日推荐开源项目：《base-admin》传送门：项目链接
推荐理由：Base Admin一套简单通用的后台管理系统，主要功能有：权限管理、菜单管理、用户管理，系统设置、实时日志，实时监控，API加密，以及登录用户修改密码、配置个性菜单等。
今日推荐英文原文：《On Election Day, Twitter battles voting misinformation》作者：Queenie Wong
原文链接：https://www.cnet.com/news/twitter-battles-misinformation-about-when-to-vote-on-election-day/
推荐理由：美国总统大选日是全美乃至全球关注的最热话题, 这期间也会有海量的fake news铺面而来. 推特作为美国人最常用的社交软件, 自然担负起和这些传言做斗争的艰巨任务.
On Election Day, Twitter battles voting misinformation
Twitter faced another onslaught of misinformation on Tuesday, including false claims that voters can cast ballots after Election Day.

The company pulled down several tweets with inaccurate information about when to vote because the posts violated the social network’s rules.

Tweets containing the false claim that people can vote on Nov. 4 depending on their political party began popping up early Tuesday as Americans headed to the polls to choose between Republican President Donald Trump and Democratic challenger Joe Biden. Polls close on Tuesday.

The false tweets are an example of the type of misinformation social networks are scrambling to combat on Election Day. Social networks, including Facebook and Twitter, have rules against posting content designed to suppress voting or intimidate people from casting their ballots. Twitter’s rules say it’ll label or remove false or misleading information about how to participate in an election.

Twitter has also been labeling and reducing the reach of tweets that contain unverified or false claims about voter fraud in Pennsylvania, a battleground state. The company labeled several tweets from Mike Roman, the Trump campaign’s director of Election Day operations, that contained misleading claims about voting. In one tweet that was labeled with a notice that states “Learn about US 2020 election security efforts,” Roman falsely claims that Democrat election officials are banning Trump poll watchers in Philadelphia. “The steal is on!,” he tweeted.

A poll watcher was denied access to one polling site in Philadelphia because of a misunderstanding about the law but was allowed into another site, PolitiFact reported. Zignal Labs, which analyzes data from social media and news outlets, said Tuesday that keywords related to “steal” or “stealing” including a hashtag that contain allegations that Democrats are trying to steal the election had more than 119,000 mentions today.

CNET found more than two dozen tweets that included inaccurate claims that either Republicans or Democrats could vote on Wednesday. It’s unclear if the tweets are jokes or were designed to deceive voters. When asked if there was an exception for satire in Twitter’s rules against voter suppression, a company spokesman said Twitter will remove tweets that violate its rules. The company didn’t say how many of these tweets have been removed, but some of them remain online.

In one of the tweets that was pulled down, a user falsely claimed that House Speaker Nancy Pelosi had passed a bill giving Democrats an extra day to vote. The user urged Democrats to head to the polls on Wednesday instead of waiting in long lines on Election Day.

In another removed tweet, a user falsely claimed that Republicans are supposed to vote on Wednesday “in order to stop larger groups at the polls because of Covid.” Some of the tweets that are still up falsely state that Election Day was split into two days for each party.

Twitter wasn’t the only social network dealing with confusing messages about the voting deadline. Facebook-owned Instagram said that on Tuesday, some users saw a message reading “Tomorrow is Election Day.” The message, actually delivered on Monday, was in the app’s cache for a “small group of people” if they hadn’t restarted the app. The notice now reads “It’s the Last Day to Vote.”

Facebook didn’t respond to questions about how much voter suppression content it’s removed.

Government officials on Tuesday warned voters about receiving scam robocalls that urge voters to vote on Wednesday because of long lines. Facebook and Twitter also suspended several right-wing news accounts on Tuesday for violating its rules, Reuters reported.

As polls continue to close across the US, social networks are also keeping their eye on premature claims of victory.

On Tuesday night, Twitter labeled a tweet from the Trump campaign that claimed victory in South Carolina. “Official sources may not have called the race when this was tweeted,” the label stated. Twitter said Monday it will consider a result official if it’s announced by a state official or the calls are made by at least two of seven national news outlets. Those outlets include ABC, the Associated Press, CBS, CNN, Fox News, NBC News or Decision Desk HQ. An identical post about South Carolina appeared on the Trump’s campaign Facebook page but wasn’t labeled for declaring premature victory. Instead, users were directed to Facebook’s Voting Information Center. First published on Nov. 3, 2020 at 4:19 p.m. PT.
下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/
开源日报第939期：《看算法 Algorithm-visualizer》

4 11 月, 2020

开源日报每天推荐一个 GitHub 优质开源项目和一篇精选英文科技或编程文章原文，坚持阅读《开源日报》，保持每日学习的好习惯。
今日推荐开源项目：《看算法 Algorithm-visualizer》
今日推荐英文原文：《Why Is It So Hard to Get Hired as a Junior Developer?》

A 今日推荐开源项目：《看算法 Algorithm-visualizer》传送门：项目链接
推荐理由：该项目名为算法可视化工具，是一个交互式的在线平台，可以从编写的代码中将算法可视化，通过程序动态展示算法运算过程。也可以修改其中的代码，从而得到不同的二叉树、列表…
今日推荐英文原文：《Why Is It So Hard to Get Hired as a Junior Developer?》作者：Samuel Martins
原文链接：https://medium.com/better-programming/why-is-it-so-hard-to-get-hired-as-a-junior-developer-920b5372f503
推荐理由：就业难，升学苦，且迷且惘且努力。
Why Is It So Hard to Get Hired as a Junior Developer?

Getting your foot in the door
Ever wondered why it is difficult for junior developers to get hired? I mean, unless you are lucky enough to get hired immediately after graduating from college or once you finish that bootcamp project, getting hired as a newbie is quite the hustle.

I have seen and heard about developers out there getting a job within a month or two of sending out applications. So why is it that at the same time, you hear about developers who have been at it for years without employment? Is the industry saturated? Are jobs being outsourced to online platforms like Upwork and Fiverr? I decided to try to get down to the bottom of this because it seems like it is a demotivating factor for promising developers looking to dive into tech.

Here is the thing: The problem is that most junior devs do not have the skills necessary to get the job. Now I know that sounds a bit unclear. Let me explain. Most junior devs apply for jobs using simple projects as part of their portfolio. Yes, I am aware that you can make a website, a calculator, a weather app, a to-do app, etc. These are all valid reasons as to why you should get a chance at a tech company, but you still do not have the skills to get in. What do I mean by that? You have to be able to prove that you can hit the ground running on day one. Say you are applying to an e-commerce company with no knowledge of what e-commerce or things like Shopify and Woo-commerce are. There is a high chance that you are not going to land that job because you have no practical skills in that field.

A lot of the companies out there are looking to take a chance on an experienced developer. Going back to the example above, employers will be more willing to take you if you have built some sort of e-commerce web app or integrated different payment gateways within a site. Having the programming knowledge of how things work alone is not enough. You need to have the practical application under your belt as well. It does not have to be a big system. You need only show that you understand the ins and outs of the system in question and the practical experience to get everything up and running should you be given the chance.

Another problem is that a lot of junior devs apply to tech giants like Google and Facebook because, well, they are the giants in tech.

To be honest, if you are starting your career, your chances of getting into the big leagues are slim. The main goal as beginner developers is usually to get hired and get your feet wet as fast as possible. What you need to do is to get a job at any company that will provide a space for you to build the experience. From there, try applying to higher-rated companies as you climb the ladder. It is going to be easier for you to get a job that way. I am not saying to not shoot for the big companies right off the bat. If you think you have a shot, go ahead, but do not put all your eggs in one basket.

It is OK to take a first job where you might get $60,000 a year rather than turning it down and expecting a call from a company that will give you $150,000.

Are the jobs there? Yes, but you need to be more skilled. A lot of successful developers started from digital agencies, freelance, or just as poorly paid interns. Then after a couple of months or a year, they get to a bigger company and keep advancing until they make it in the developer world.

Let me make this crystal-clear: There is no company out there that will be willing to hire you when your portfolio is full of YouTube course simple projects. Change them, make them your own, combine different related projects into one. Anything that can make the employer see that you can be creative enough to create a problem and still be able to solve it. Go outside the box. If you want to create a chat app, go ahead. Make sure you polish it up, though. Make good use of best database practices, UI/UX elements, API calls, etc. to impress the employer to the point where not hiring you would be a loss to them.

Another thing junior developers seem to forget is that a lot of people can code these days. A lot of people out there can follow a tutorial and make an app or a website even without learning how to code. The big question is, how are you going to differentiate yourself from everybody? You need to have projects that make you stand out as a professional. A person that the company wants. A person who can bring value.

If you are applying for a front-end position, make the employer see that you know how to work it like a beast. Go to a site like Behance for design inspiration, then tweak some of it to give your project a little bit of uniqueness! Do not expect to get hired with shoddy work. The same applies to back-end and full-stack applicants. Companies need to make sure that they are going to spend hundreds of thousands of dollars on top-notch developers. No one wants to hire a developer, only to take them back to training for months — unless you applied for an internship position.

There has never been a perfect developer. There will never be one because of just how much tech is changing. You are not expected to know every technology. Stick with the stack you set out to learn. Become so good at it that no one will be able to doubt your skills.

There is something I learned from a developer named Victoria Sun in a YouTube video from a couple of years ago. She said, “Be true to yourself and let your work speak for you because ultimately, they cannot ignore you if you do amazing stuff.” That drives me to become better every day, and that is the advice I’d give my younger self and any other person looking to go into tech.

下载开源日报APP：https://opensourcedaily.org/2579/
加入我们：https://opensourcedaily.org/about/join/
关注我们：https://opensourcedaily.org/about/love/