Top 3 winners will get monetary prizes, badges, and certificates of recognition.\u00a0\u00a0<\/p>

• \t

  \ud83e\udd47First prize \u2013 300 USD + Swag\u00a0<\/p>\t<\/li>\t

• \t

  \ud83e\udd48Second prize \u2013 150 USD\u00a0+ Swag\u00a0<\/p>\t<\/li>\t

• \t

  \ud83e\udd49Third prize \u2013 50 USD\u00a0+ Book of the industry expert\u00a0<\/p>\t<\/li><\/ul>

  In addition, we will have some outstanding entries who will receive certificates of participation and ShiftSync badges (based on your points).\u00a0<\/p><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>

  \u00a0If you have any concerns or need assistance, feel free to reach out to shiftsync@tricentis.com<\/a>\u00a0or message\u00a0@Kat<\/user-mention>\u00a0or\u00a0@Daria<\/user-mention>.<\/p>

  You must watch out for these dates<\/strong>:\u00a0<\/p>

  • \t

    Blog submission last date \u2013 July 30, 2023\u00a0<\/p>\t<\/li>\t

  • \t

    ShiftSync assessment \u2013 August 16, 2023\u00a0<\/p>\t<\/li>\t

  • \t

    Winner announcement \u2013 August 18, 2023\u00a0<\/p>\t<\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>

    After blog submission, you can vote for your fellow users\u2019 blogs. The most popular blogs in terms of likes and comments will be shortlisted. Public voting is open for 14 days (about 2 weeks) after submission. In other words, if you submit the blog on July 19, your votes will be counted for 14 days, starting from July 19\u00a0to August 1. If you submit your blog on July 30, you will still get 14 days of voting, which means your votes will be counted from July 30 till August 12.\u00a0\u00a0<\/p>

    Please make sure that you submit your blogs on or before July 30, 2023. Post July 30, your blogs won\u2019t be accepted.\u00a0\u00a0<\/span><\/strong><\/p>

    ShiftSync will finalize the top 3 winners based on public voting.\u00a0<\/strong>\u00a0<\/p>

    An opportunity for you all to create blogs on the new community and win prizes. We\u2019re encouraging you to create some meaningful and engaging content with utmost brevity. Get ready to awaken your creative muse. Grab the opportunity to educate your fellow users as well as encourage them to be a part of it.\u00a0\u00a0<\/p><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>

    How to be a part of this Blogathon?\u00a0<\/h3>

    1. \t

       Submit your blog to the ShiftSync community.<\/u><\/a> Please reply to the blogathon topic. Screenshot attached.\u00a0<\/p>\t<\/li><\/ol>

       <\/figure>

       \u00a0<\/p>

       1. Create your original blog posts (between 300-1000 words<\/strong>) and cover ONE of the following topics:\u00a0<\/li><\/ol>
          • \ud83d\udcc3Test Automation for Mobile Applications<\/strong> \u2013This is a broad topic, so feel free to pick your own point of view: from how it contributes to company success or share some examples from your experience (both positive or challenges and learnings).<\/li>\t
          • \ud83d\udcc3What's enough testing?<\/strong><\/li>\t
          • \ud83d\udcc3Integrating OAuth 2.0 in C# Microservices: A Step-by-Step Guide.<\/strong>\u00a0<\/li><\/ul><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>
            1. Follow the rules:<\/li><\/ol>
               • An author can submit multiple blogs; however, they must cover the topics listed above\u00a0\u00a0\u00a0<\/li>\t
               • The entry should be in English\u00a0<\/li>\t
               • The entry should not have multiple authors\u00a0<\/li>\t
               • Don't forget to mention the title of the blog that you chose\u00a0\u00a0<\/li>\t
               • Please include images (not more than 5) to make your blog visually appealing. You can use images from pexels<\/u><\/a> or unsplash<\/u><\/a>\u00a0<\/li><\/ul>

                 Who can vote?\u00a0<\/strong><\/p>

                 • Anyone\u00a0<\/li>\t
                 • You cannot vote your own blog but go ahead and activate your network and friends, have them vote for you and get your name and article to the top of the list!\u00a0<\/li><\/ul>","quoteUsername":"Kat","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">
                   • 就像
                   • 报价和回复
                   • 分享

          ---

          20个回复

          

          Userlevel 2

          + 1

          • ahmfo
          • 员工
          • 1回复
          • 11天前

            2023年7月26日

          

          第1部分:重大的决定

          工程师通常包括关键决策的旅程。你发现自己在一个岔路口,你应该与一个OAuth提供者集成Auth0或建立自己的OAuth服务吗?而建立你自己的服务可能看起来像一个诱人的冒险,与一个可靠的供应商合作Auth0往往使旅程更平稳和更快。

          第2部分:跳舞OAuth流动

          OAuth 2.0舞蹈不同的节奏,每一个曲调代表一个不同的流动——授权代码,隐式密码凭据和客户端凭据。每个舞蹈,或流,有独特的节奏适合一个特定的场景。

          授权代码流

          通常被认为是服务器端应用程序的节奏,授权代码流是完美的,当你的源代码不暴露给公众。一个典型的microservices设置可能跳舞这个节奏。这是一个简化的c#代码片段使用一个OAuth2客户端实现这个流像IdentityModel:

          var客户= new HttpClient ();
          
          var迪斯科=等待client.GetDiscoveryDocumentAsync (“https://your-identity-server”);
          如果disco.IsError抛出新的异常(disco.Error);
          
          var =等待客户回应。RequestAuthorizationCodeTokenAsync(new AuthorizationCodeTokenRequest
          {
          地址= disco.TokenEndpoint,
          ClientId = " client_id”,
          ClientSecret = " client_secret ",
          代码=“authorization_code”,
          RedirectUri = " redirect_uri "
          });
          
          如果response.IsError抛出新的异常(response.Error);
          
          Console.WriteLine (response.Json);
          

          
          

          隐式流

          隐流,类似于一个活泼跳汰机,是一种简化的流最初设计为基于javascript应用程序所有代码和资源加载前期,没有后端来安全地储存令牌。在这种流,直接从授权请求返回一个访问令牌。

          虽然它提供了快速和简单的实现,这个流已然失宠在很多情况下由于安全问题,如公开令牌在浏览器的URL。这是类似于跳舞没有安全网,不建议可以使用授权代码的应用程序流。

          这是一个广义的隐式流是如何工作的:

          window.location。href = ' https://your-identity-server/authorize?
          response_type =令牌
          client_id = $ {clientId}
          &redirect_uri = $ {redirectUri}
          范围范围= $ {}';
          
          / /访问令牌将在重定向URL
          

          
          

          * *请注意,这段代码是在JavaScript中隐式流动通常是实现基于JavaScript的前端,而不是一个c#端。* *

          密码凭证流

          想象的密码凭证流慢华尔兹,熟悉但往往更不安全。这是专为高度受信任应用程序的用户的凭证直接交换访问令牌。这是不太常见的由于其潜在的滥用和不推荐,除非绝对必要的。

          一个通用的例子流的样子:

          var =等待客户回应。RequestPasswordTokenAsync(new PasswordTokenRequest
          {
          地址= disco.TokenEndpoint,
          ClientId = " client_id”,
          ClientSecret = " client_secret ",
          用户名= "用户名",
          密码=“密码”,
          范围= " api1 "
          });
          
          如果response.IsError抛出新的异常(response.Error);
          Console.WriteLine (response.Json);
          

          
          

          客户端凭证流

          最后,客户端凭证流,迅速探戈服务器到服务器的通信。在这个舞蹈,不涉及用户交互。相反,客户机应用程序直接验证本身并检索一个访问令牌。它适合后台服务的客户端之间高度的信任和授权服务器。

          这是一个c#代码片段展示这个流:

          var =等待客户回应。RequestClientCredentialsTokenAsync(new ClientCredentialsTokenRequest
          {
          地址= disco.TokenEndpoint,
          ClientId = " client_id”,
          ClientSecret = " client_secret ",
          范围= " api1 "
          });
          
          如果response.IsError抛出新的异常(response.Error);
          Console.WriteLine (response.Json);
          

          请记住每个OAuth 2.0流服务特定的用例,并选择适当的流动应该基于您的应用程序的需求和安全注意事项。

          第3部分:零信任并刷新令牌的力量

          拥抱的口头禅“从不信任,总是验证。”The Zero Trust model ensures every request is authenticated and authorized, irrespective of its origin. Implementing this in OAuth involves regularly refreshing tokens. Here's a simple C# example of how a refresh token can be used:

          var =等待客户回应。RequestRefreshTokenAsync(new RefreshTokenRequest
          {
          地址= disco.TokenEndpoint,
          ClientId = " client_id”,
          ClientSecret = " client_secret ",
          RefreshToken = " refresh_token "
          });
          
          如果response.IsError抛出新的异常(response.Error);
          
          Console.WriteLine (response.Json);
          

          
          

          第4部分:前端后端——您值得信赖的伙伴

          结束你的旅程的后端前端(BFF)模式。你的BFF处理与授权服务器交互,维护客户的秘密,并管理令牌。这是如何通过一个访问令牌从你的BFF microservice在c#中:

          var客户= new HttpClient ();
          
          client.SetBearerToken (“access_token”);
          
          var =等待client.GetAsync反应(“https://your-microservice”);
          
          如果(! response.IsSuccessStatusCode)抛出新的异常(response.StatusCode.ToString ());
          
          var内容=等待response.Content.ReadAsStringAsync ();
          Console.WriteLine(内容);
          

          
          

          总之,跳舞OAuth 2.0看似复杂,但正确的步骤,您可以构建安全、高效的c# microservices。记住,它是关于选择正确的舞蹈,了解节奏,使用正确的工具。

          当我们结束我们的旅程通过OAuth 2.0 c# Microservices,我们希望您发现了这个指导帮助和照明。OAuth之舞看起来复杂,但是每走一步,你就会掌握节奏,创造安全、高效的应用程序。

          如果你喜欢这篇文章或发现它有用,不要犹豫去喜欢它,分享它与你的开发人员。你的反馈是什么驱使我们创造更多这样的内容,所以请离开你的想法,下面的评论,或问题。我们继续谈话,加深我们对这些基本的理解主题。编码快乐!

          <\/figure>

          Part 1: The Big Decision<\/h2>

          The journey of an engineer often involves making pivotal decisions. You find yourself at a fork in the road - should you integrate with an OAuth provider like Auth0 or build your own OAuth service? While building your own service may seem like an enticing adventure, partnering with a reliable provider like Auth0 often makes the journey smoother and faster.<\/p>

          Part 2: Dancing with OAuth Flows<\/h2>

          OAuth 2.0 dances to different rhythms, each tune representing a different flow - Authorization Code, Implicit, Password Credentials, and Client Credentials. Each dance, or flow, has a unique rhythm suited to a particular scenario.<\/p>

          \u00a0The Authorization Code Flow<\/h3>

          Often considered the rhythm of server-side applications, the Authorization Code Flow is perfect when your source code isn't exposed to the public. A typical microservices setup may dance to this rhythm. Here's a simplified C# snippet implementing this flow using an OAuth2 client like IdentityModel:<\/p>

          var client = new HttpClient();
          
          var disco = await client.GetDiscoveryDocumentAsync(\"https:\/\/your-identity-server\");
          if (disco.IsError) throw new Exception(disco.Error);
          
          var response = await client.RequestAuthorizationCodeTokenAsync(new AuthorizationCodeTokenRequest
          {
              Address = disco.TokenEndpoint,
              ClientId = \"client_id\",
              ClientSecret = \"client_secret\",
              Code = \"authorization_code\",
              RedirectUri = \"redirect_uri\"
          });
          
          if (response.IsError) throw new Exception(response.Error);
          
          Console.WriteLine(response.Json);
          <\/code><\/pre>
          
          \u00a0<\/p>
          The Implicit Flow<\/h3>
          The Implicit Flow, akin to a lively jig, is a simplified flow initially designed for JavaScript-based applications where all code and resources are loaded upfront, and there is no backend to securely store tokens. In this flow, an access token is returned directly from the authorization request.\u00a0<\/p>
          While it offers swift and straightforward implementation, this flow has fallen out of favor in many scenarios due to security concerns, such as exposing tokens in the browser URL. It's akin to dancing without a safety net and is not recommended for applications that can use Authorization Code Flow.<\/p>
          Here's a generalized view of how the Implicit Flow works:<\/p>
          \u00a0<\/p>
          window.location.href = `https:\/\/your-identity-server\/authorize?
              response_type=token
              &client_id=${clientId}
              &redirect_uri=${redirectUri}
              &scope=${scope}`;
          
          \/\/ The access token will be in the redirected URL
          <\/code><\/pre>
          
          \u00a0<\/p>
          **Please note that this code is in JavaScript as Implicit Flow is typically implemented in a JavaScript-based frontend, not a C# backend.**<\/p>
          The Password Credentials Flow<\/h3>
          Imagine the Password Credentials Flow as a slow waltz, familiar yet often less secure. It was designed for highly trusted applications where the user's credentials are exchanged directly for access tokens. It's less common due to its potential for misuse and is not recommended unless absolutely necessary.<\/p>
          A generic example of this flow might look like:<\/p>
          \u00a0<\/p>
          var response = await client.RequestPasswordTokenAsync(new PasswordTokenRequest
          {
              Address = disco.TokenEndpoint,
              ClientId = \"client_id\",
              ClientSecret = \"client_secret\",
              UserName = \"username\",
              Password = \"password\",
              Scope = \"api1\"
          });
          
          if (response.IsError) throw new Exception(response.Error);
          Console.WriteLine(response.Json);
          <\/code><\/pre>
          
          \u00a0<\/p>
          The Client Credentials Flow<\/h3>
          Lastly, the Client Credentials Flow, the swift tango of server-to-server communication. In this dance, no user interaction is involved. Instead, a client application authenticates itself and retrieves an access token directly. It's suitable for background services where there's a high degree of trust between the client and the authorization server.<\/p>
          Here's a C# snippet showcasing this flow:<\/p>
          var response = await client.RequestClientCredentialsTokenAsync(new ClientCredentialsTokenRequest
          {
              Address = disco.TokenEndpoint,
              ClientId = \"client_id\",
              ClientSecret = \"client_secret\",
              Scope = \"api1\"
          });
          
          if (response.IsError) throw new Exception(response.Error);
          Console.WriteLine(response.Json);
          <\/code><\/pre>
          Please remember that each OAuth 2.0 flow serves specific use cases, and the appropriate flow should be selected based on the needs and security considerations of your application.<\/p>
          Part 3: The Power of Zero Trust and Refresh Tokens<\/h2>
          Embrace the mantra of \"never trust, always verify.\" The Zero Trust model ensures every request is authenticated and authorized, irrespective of its origin. Implementing this in OAuth involves regularly refreshing tokens. Here's a simple C# example of how a refresh token can be used:<\/p>
          \u00a0<\/p>
          var response = await client.RequestRefreshTokenAsync(new RefreshTokenRequest
          {
              Address = disco.TokenEndpoint,
              ClientId = \"client_id\",
              ClientSecret = \"client_secret\",
              RefreshToken = \"refresh_token\"
          });
          
          if (response.IsError) throw new Exception(response.Error);
          
          Console.WriteLine(response.Json);
          <\/code><\/pre>
          
          \u00a0<\/p>
          Part 4: Backend for Frontend \u2013 Your Trusty Sidekick<\/h2>
          End your journey with the Backend for Frontend (BFF) pattern. Your BFF handles interactions with the authorization server, maintains client secrets, and manages tokens. Here's how you can pass an access token from your BFF to a microservice in C#:<\/p>
          \u00a0<\/p>
          var client = new HttpClient();
          
          client.SetBearerToken(\"access_token\");
          
          var response = await client.GetAsync(\"https:\/\/your-microservice\");
          
          if (!response.IsSuccessStatusCode) throw new Exception(response.StatusCode.ToString());
          
          var content = await response.Content.ReadAsStringAsync();
          Console.WriteLine(content);
          <\/code><\/pre>
          
          \u00a0<\/p>
          In conclusion, dancing with OAuth 2.0 may seem complex, but with the right steps, you can build secure and efficient C# microservices. Remember, it's about choosing the right dance, understanding the rhythms, and using the right tools.<\/p>
          \u00a0<\/p>
          As we wrap up our journey through OAuth 2.0 in C# Microservices, we hope you found this guide helpful and illuminating. The dance of OAuth may seem complex, but with each step, you'll master the rhythm and create secure, efficient applications.<\/p>
          If you enjoyed this article or found it useful, don't hesitate to like it and share it with your fellow developers. Your feedback is what drives us to create more content like this, so please leave your thoughts, comments, or questions below. Let's continue the conversation and deepen our understanding of these essential topics together. Happy coding!<\/p>","quoteUsername":"ahmfo","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">
                      
          
                       
          就像
                       
          报价和回复
                      
                     

          ---

          N

          Userlevel 1

          • NehaAsthana
          • 3回复
          • 10天前

            2023年7月27日

          足够的测试是什么?

          测试是一个微妙的平衡由“测试人员”将以在被测系统的混乱。它是人类的识别和精神状态紧密相连。如果你是一个满足的人,它将描述在你的测试。相反当头脑不安他们可能转向两个极端:要么你需要一个更简单的途径迟钝地把它委托给他人或精度不照顾你的工作和/或第二路径进入环形完美。后者促使每个人工作过度,导致倦怠虽然仍感觉不满的测试在给定的时间。

          

          我们怎么知道被测系统是否被正确审查,金色的中间。我们必须为自己和团队开发指南记住,它不是一个放之四海而皆准的最佳实践文档。每个上下文都是独特的和方法应该适应。现在同样会医生治疗所有疾病的药吗?这对医生和病人都将是灾难性的!

          一个有用的指南是设置一些陷阱,让被测系统自由漫游,揭示其然后找到一种方法来克服这些弱点。如果它不能在陷阱,然后挖掘问题的根源。必须承认,它可能不是一个缺陷,而可能是一个有用的信息来设置陷阱在未来!测试人员拥有原始猎人的本能,在这种情况下他们寻找bug。错误是软件开发周期的固有部分,只要人类参与这个过程。188金宝搏官网登录app

          无论你的动机是挤压太多bug或获得可见性作为专家测试,最终目标应该是实现质量。叫自己质量师、质量评论家,而称自己仅仅是测试人员因为测试人员不断改变帽子的一个目标让更多的产品质量。我将结束测试足够当你认为理想的质量。

          为了进一步提高我们的测试过程,让我们深入研究一些具体的例子和测试技术。例如,探索性测试允许我们来模拟真实的场景,回归测试有助于确保新变化不引入新问题,和边界测试验证系统正确处理极端值。通过明智的将这些技术,我们可以增加我们的测试工作并交付更高质量的产品。

          我们在测试中经常面临的一个挑战是时间限制。关键是承认这一现实和有效地优化我们的努力。识别的关键功能和高危地区,专注于彻底的测试,同时还给予合理注意系统的其他部分。

          总之,测试是足够的,当我们认为所需的质量水平。遵循一个明确的指导方针,采用各种测试技术,和承认时间限制,测试人员可以有效地平衡他们的努力和贡献的成功产品测试。接受测试的动态特性,不断调整和完善你的方法来满足每个项目的独特要求。

          \u00a0<\/p>

          What\u2019s enough testing?<\/strong><\/p>

          Testing is a delicate balancing act<\/strong> performed\u00a0by \u201cTesters\u201d to bring in order to the chaos within the system under test. It is closely connected to human congnition and\u00a0state of mind. If you are a satisfied person, it will depict in your testing.\u00a0Conversely when the minds are unsettled they may veer towards two extremes:\u00a0either you would take an easier route of lethargically delegating it to others or not taking care of precision in your work and\/or second path of going into endless perfection loop. The latter pushes\u00a0everyone to work excessively, resulting in burnout while still feeling discontented with the amount of testing achieved in given time.<\/p>

          

          ---

          年代

          Userlevel 4

          • sangeetha
          • 亚音速0.5
          • 2回答
          • 10天前

            2023年7月27日

          足够的测试是什么?

          

          “足够的测试”是指进行足够的测试,确保软件产品的质量和可靠性,系统或应用程序之前发布给最终用户。188金宝搏官网登录app测试的主要目标是识别并修复缺陷、缺陷或任何问题,可能会影响软件的功能和性能。188金宝搏官网登录app

          所需的确切数量的测试可以取决于软件的复杂性等因素,应用程序的临界,目标用户群,项目的时间和预算。188金宝搏官网登录app下面是一些常见的测试类型可以导致整个测试工作:

          

          确定足够的测试,开发团队和利益相关者必须考虑到他们愿意接受的风险程度,如何相信他们需要在软件的质量。188金宝搏官网登录app目标100% bug软件通常是不切实际的,但测试应188金宝搏官网登录app该足够全面减轻重大风险,确保软件符合最小可接受的质量水平。

          

          也是必要的平衡测试工作与项目约束、时间和预算等详尽的测试可能并不总是可行的。利用测试管理实践和基于风险的测试方法可以帮助测试工作关注领域最重要软件的成功。188金宝搏官网登录app此外,从终端用户获得反馈,将他们的输入测试过程可以在提炼有价值的软件,使其更加以用户为中心。188金宝搏官网登录app

          记住,测试是一个持续的过程,其关键持续监控处理系统的性能在实际条件和更新所需的模型作为维护其准确性和有效性。重要的是要承认“足够测试”并不意味着软件是完全没有缺陷或无风险。188金宝搏官网登录app测试产品的质量提供了有价值的信息,但它不能保证软件是完全没有错误。188金宝搏官网登录app因此,关键是找到一个平衡的实际约束和信心的水平在软件的性能。188金宝搏官网登录app

          结论测试是一个无穷无尽的过程,和继续,直到软件存在。188金宝搏官网登录app这不是不可能找到所有的软件缺陷,但肯定,这不是决定性因素停止测试。188金宝搏官网登录app

          What\u2019s enough testing?<\/span><\/span><\/strong><\/p>

          \u00a0<\/p>

          

          ---

          N

          Userlevel 1

          • NehaAsthana
          • 3回复
          • 10天前

            2023年7月27日

          @Kat为什么没有人能够像我的帖子?我的同事说这表明喜欢一会儿,撤回。你能帮助吗?

          @Kat<\/user-mention>\u00a0Why is nobody able to like my post? My colleagues are saying it shows liked for a moment and withdraws back. Can you please assist?<\/p>","quoteUsername":"NehaAsthana","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

          • 就像
          • 报价和回复

          ---

          

          Userlevel 5

          + 2

          • 凯特
          • 作者
          • 社区经理
          • 72回复
          • 10天前

            2023年7月27日

          @Kat为什么没有人能够像我的帖子?我的同事说这表明喜欢一会儿,撤回。你能帮助吗?

          你好,我检查,一切正常。也许他们不是注册在社区。

          质量问题,凯特

          \t

          @Kat<\/user-mention>\u00a0Why is nobody able to like my post? My colleagues are saying it shows liked for a moment and withdraws back. Can you please assist?<\/p>\t<\/div><\/content-quote>

          Hi, I checked it, everything works. Maybe they are not registered in the community.\u00a0<\/p>","quoteUsername":"Kat","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

          • 就像
          • 报价和回复

          ---

          N

          Userlevel 1

          • NehaAsthana
          • 3回复
          • 10天前

            2023年7月27日

          @Kat为什么没有人能够像我的帖子?我的同事说这表明喜欢一会儿,撤回。你能帮助吗?

          你好,我检查,一切正常。也许他们不是注册在社区。

          他们却抱怨像消失的那一刻,他们按按钮在页面上。我也测试和它的发生。

          \t

          \t\t

          \t\t

          @Kat<\/user-mention>\u00a0Why is nobody able to like my post? My colleagues are saying it shows liked for a moment and withdraws back. Can you please assist?<\/p>\t\t<\/div>\t\t<\/div>\t<\/content-quote>

          Hi, I checked it, everything works. Maybe they are not registered in the community.\u00a0<\/p>\t<\/div><\/content-quote>

          They have but are complaining that their like disappears the moment they press like button on the page. I too tested out and its happening.<\/p>","quoteUsername":"NehaAsthana","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

          • 就像
          • 报价和回复

          ---

          

          Userlevel 5

          + 2

          • 凯特
          • 作者
          • 社区经理
          • 72回复
          • 10天前

            2023年7月27日

          @Kat为什么没有人能够像我的帖子?我的同事说这表明喜欢一会儿,撤回。你能帮助吗?

          你好,我检查,一切正常。也许他们不是注册在社区。

          他们却抱怨像消失的那一刻,他们按按钮在页面上。我也测试和它的发生。

          你能给我他们的用户名直接的消息吗?它可能发生,因为他们还没有证实了他们的电子邮件。

          质量问题,凯特

          \t

          \t\t

          \t\t

          \t\t\t

          \t\t\t

          \t\t\t

          @Kat<\/user-mention>\u00a0Why is nobody able to like my post? My colleagues are saying it shows liked for a moment and withdraws back. Can you please assist?<\/p>\t\t\t<\/div>\t\t\t<\/div>\t\t\t<\/div>\t\t<\/content-quote>

          Hi, I checked it, everything works. Maybe they are not registered in the community.\u00a0<\/p>\t\t<\/div>\t\t<\/div>\t<\/content-quote>

          They have but are complaining that their like disappears the moment they press like button on the page. I too tested out and its happening.<\/p>\t<\/div><\/content-quote>

          Could you please send me their usernames in direct messages?\u00a0It may happen because they haven\u2019t confirmed their emails.\u00a0<\/p>","quoteUsername":"Kat","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

          • 就像
          • 报价和回复

          ---

          V

          • VINOB6
          • 1回复
          • 9天前

            2023年7月27日

          标题:移动应用程序的自动化测试

          在当今快节奏的数字时代,移动应用已经成为我们生活的一个基本组成部分。手机应用程序的使用导致了上升的增加对高品质的需求,没有错误,用户友好的应用程序。为了满足这些预期,开发人员必须确保他们的移动应用程序在向公众发布之前进行严格的测试。移动应用测试自动化已经成为一个重要的解决方案,加快测试过程,同时保持应用的质量和可靠性。

          移动应用程序开发需要处理大量的设备,操作系统,屏幕尺寸。手工测试,虽然重要,不仅费时而且效率不高时覆盖大量的测试场景。测试自动化提供了几个关键的好处,有助于一个更精简更健壮的测试过程:

          加速测试:自动化工具使开发人员能够同时运行多个测试,大大降低测试时间比手工测试。这种加速测试确保更快的发布周期和更快的上市时间为移动应用程序。

          增加测试覆盖率:与越来越多的移动设备和操作系统版本,手动覆盖所有组合几乎是不可能的。测试自动化综合测试覆盖率在各种设备上通过执行测试脚本和配置。

          一致性和可重复性:自动化测试产生一致的和可重复的结果,确保可以多次执行相同的测试没有影响结果的人为错误的风险。

          早期错误检测:早期识别错误和问题在开发过程中节省时间和资源。测试自动化进行持续集成和早期的故障检测,便于及时修复和顺畅的开发周期。

          成本效益:而自动化测试的初始设置可能需要投资,它证明成本效益在长远来看,由于减少了人工操作和更快的上市时间。

          选择合适的自动化测试工具

          选择合适的测试自动化工具对成功的手机应用程序测试是至关重要的。广泛的工具,每种方法都有其优势和弱点。一些流行的自动化测试框架的移动应用程序包括:

          Appium:Appium是一个开源、跨平台的自动化工具,允许开发人员测试本机,混合和移动web应用程序。它支持各种编程语言和无缝集成提供了流行的开发环境。

          咖啡:由谷歌开发的,咖啡是一种强大的自动化框架设计测试Android应用程序。它提供了一组丰富的功能,包括应用程序的UI线程同步和能够处理复杂的手势。

          XCUITest:XCUITest是官方苹果的iOS应用程序的自动化框架。它提供了出色的支持iOS-specific元素和交互,使它趋之若鹜的选择iphone和ipad上测试应用程序。

          Selendroid:Selendroid是一个开源框架专门针对测试Android应用程序。它支持多个设备同时提供强大的本地和混合应用程序的处理。

          排毒:排毒是一个受欢迎的端到端测试反应本机应用程序的框架。它允许开发人员来模拟用户交互和Android和iOS设备上验证应用程序的行为。

          测试自动化在移动应用程序开发的最佳实践

          而自动化测试可以提高效率和有效性,它的成功依赖于最佳实践:

          早期的测试包括:将测试从应用程序开发的初始阶段尽早识别和解决问题。这减少了缺陷的机会积累,影响应用程序的整体质量。

          设备和操作系统覆盖范围:旨在测试在各种各样的实际设备和操作系统版本。首次测试仿真器和仿真器是有价值的,但可能无法复制所有真实的场景。

          维护测试脚本:创建结构良好的、可维护的测试脚本,以确保可伸缩性的应用发展。频繁的更新和变化不应该导致一个完整的测试套件的检修。

          持续集成:实现持续集成实践每次代码提交后自动运行测试。这个艾滋病早期错误检测,并确保应用程序仍然是稳定的整个开发过程。

          用户体验测试:除了功能测试,优化用户体验测试,以确保应用程序直观和用户友好。

          在不断扩展的移动应用程序,测试自动化已经成为开发过程中不可缺少的一部分。通过利用自动化工具和最佳实践后,开发人员可以提高测试覆盖率,及早发现bug,交付高质量的移动应用用户以更有效的和有效的方式。接受测试自动化不仅节省时间和资源,还有助于建立一个忠实的用户群,提供可靠的和用户友好的移动应用程序。随着移动应用景观继续发展,自动化测试仍将是至关重要的组件在向全球用户提供特殊应用的经验。

          Title: Test Automation for Mobile Applications<\/strong><\/p>

          In today's fast-paced digital age, mobile applications have become an fundamental part of our lives. The rise in mobile app usage has led to an increased demand for high-quality, bug-free, and user-friendly applications. To meet these expectations, developers must ensure that their mobile apps undergo rigorous testing before being released to the public. Test automation for mobile applications has emerged as a crucial solution to expedite the testing process while maintaining the app's quality and reliability.<\/p>

          Mobile application development involves dealing with a myriad of devices, operating systems, and screen sizes. Manual testing, though essential, is time-consuming and inefficient when it comes to covering the vast array of test scenarios. Test automation offers several key benefits that contribute to a more streamlined and robust testing process:<\/p>

          Accelerated Testing:<\/strong> Automation tools allow developers to run multiple tests simultaneously, significantly reducing testing time compared to manual testing. This accelerated testing ensures quicker release cycles and faster time-to-market for mobile apps.<\/p>

          Increased Test Coverage:<\/strong> With an ever-growing number of mobile devices and operating system versions, it is practically impossible to cover all combinations manually. Test automation enables comprehensive test coverage by executing test scripts on various devices and configurations.<\/p>

          Consistency and Repeatability: <\/strong>Automated tests produce consistent and repeatable results, ensuring that the same tests can be executed multiple times without the risk of human errors affecting the outcome.<\/p>

          Early Bug Detection:<\/strong> Identifying bugs and issues early in the development process saves time and resources. Test automation enables continuous integration and early bug detection, facilitating prompt fixes and smoother development cycles.<\/p>

          Cost-Effectiveness:<\/strong> While the initial setup of test automation may require investment, it proves cost-effective in the long run due to reduced manual effort and faster time-to-market.<\/p>

          Choosing the Right Test Automation Tools<\/p>

          Selecting the appropriate test automation tools is crucial for successful mobile app testing. A wide range of tools are available, each with its strengths and weaknesses. Some popular test automation frameworks for mobile apps include:<\/p>

          Appium:<\/strong> Appium is an open-source, cross-platform automation tool that allows developers to test native, hybrid, and mobile web applications. It supports various programming languages and provides seamless integration with popular development environments.<\/p>

          \u00a0<\/p>

          Espresso:<\/strong> Developed by Google, Espresso is a powerful automation framework designed for testing Android applications. It offers a rich set of features, including synchronization with the app's UI thread and the ability to handle complex gestures.<\/p>

          \u00a0<\/p>

          XCUITest:<\/strong> XCUITest is Apple's official automation framework for iOS apps. It provides excellent support for iOS-specific elements and interactions, making it a go-to choice for testing applications on iPhones and iPads.<\/p>

          Selendroid:<\/strong> Selendroid is an open-source framework specifically tailored for testing Android applications. It supports multiple devices simultaneously and offers robust handling of native and hybrid apps.<\/p>

          Detox:<\/strong> Detox is a popular end-to-end testing framework for React Native applications. It allows developers to simulate user interactions and verify app behavior on both Android and iOS devices.<\/p>

          Best Practices for Test Automation in Mobile App Development<\/p>

          While test automation can enhance efficiency and effectiveness, its success relies on following best practices:<\/p>

          Early Test Inclusion:<\/strong> Incorporate testing from the initial stages of app development to identify and address issues as early as possible. This reduces the chances of defects accumulating and affecting the app's overall quality.<\/p>

          Device and OS Coverage:<\/strong> Aim to test on a diverse range of real devices and operating system versions. Emulators and simulators are valuable for initial testing but may not replicate all real-world scenarios.<\/p>

          Maintainable Test Scripts:<\/strong> Create well-structured and maintainable test scripts to ensure scalability as the app evolves. Frequent updates and changes should not lead to a complete overhaul of the test suite.<\/p>

          Continuous Integration:<\/strong> Implement continuous integration practices to run tests automatically after each code commit. This aids in early bug detection and ensures that the app remains stable throughout the development process.<\/p>

          User Experience Testing:<\/strong> Apart from functional testing, prioritize user experience testing to ensure the app is intuitive and user-friendly.<\/p>

          In the ever-expanding world of mobile applications, test automation has become an indispensable part of the development process. By leveraging automation tools and following best practices, developers can enhance test coverage, identify bugs early, and deliver high-quality mobile apps to users in a more efficient and cost-effective manner. Embracing test automation not only saves time and resources but also contributes to building a loyal user base by providing reliable and user-friendly mobile applications. As the mobile app landscape continues to evolve, test automation will remain a vital component in delivering exceptional app experiences to users worldwide.<\/p>","quoteUsername":"VINOB6","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

          • 就像
          • 报价和回复

          ---

          年代

          Userlevel 4

          • sangeetha
          • 亚音速0.5
          • 2回答
          • 9天前

            2023年7月27日

          @Kat为什么没有人能够像我的帖子?我的同事说这表明喜欢一会儿,撤回。你能帮助吗?

          你好,我检查,一切正常。也许他们不是注册在社区。

          \t

          \t

          \t

          \t\t

          \t\t

          \t\t

          \t\t

          @Kat<\/user-mention>\u00a0Why is nobody able to like my post? My colleagues are saying it shows liked for a moment and withdraws back. Can you please assist?<\/p>\t\t<\/div>\t\t<\/div>\t\t<\/div>\t\t<\/div>\t<\/content-quote>

          Hi, I checked it, everything works. Maybe they are not registered in the community.\u00a0<\/p>\t<\/div>\t<\/div>\t<\/div><\/content-quote>

          \u00a0<\/p>","quoteUsername":"sangeetha","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

          • 就像
          • 报价和回复

          ---

          R

          • Rishabh
          • 亚音速0.7
          • 1回复
          • 8天前

            2023年7月29日

          

          我们非常高兴宣布第一blogathon,我们热忱邀请您参与,展示你的特殊技术和写作技巧!

          这不是普通的竞争,人。这是一个机会与志趣相投的人,炫耀你的专长,给你的文章应有的关注,谁知道呢,你可能只是抓拍一些奖品!

          鼓励更多的人向博客写作,ShiftSync推出一个月Blogathon比赛2023年7月19日,2023年8月18日。

          前三赢家将获得货币奖励,徽章,和证书的认可。

          • 一等奖- 300美元+赃物

          • 二等奖- 150美元+赃物

          • 三等奖- 50美元+书行业的专家

          此外,我们将有一些杰出的条目将获得证书的参与和ShiftSync徽章(根据你的点)。

          如果你有任何问题或需要帮助,随时联系shiftsync@188金宝搏app苹果下载软件tricentis.com或消息 @Kat或 @Daria。

          你必须小心这些日期:

          • 博客提交过去的日子——2023年7月30日

          • ShiftSync评估——2023年8月16日

          • 赢家- 8月18日宣布,2023年

          博客提交之后,可以把票投给你的用户的博客。最受欢迎的博客而言,喜欢和评论将入围。公众投票开放14天提交后(约2周)。换句话说,如果你提交博客7月19日,你的投票数为14天,从7月19日至8月1日。如果你提交你的博客7月30日,你仍然会得到14天的投票,这意味着你的票将会从7月30日到8月12日计算。

          请确保你在7月30日或之前提交您的博客,2023人。7月30日,你的博客不会被接受。

          ShiftSync将完成基于公众投票前三的赢家。

          你所有的机会在新创建的博客社区,赢得奖品。我们鼓励你创建一些有意义的和引人入胜的内容极其简洁。准备唤醒你的创作灵感。抓住机会让你的用户以及鼓励他们成为它的一部分。

          如何成为一个Blogathon的一部分吗?

          1. 提交你的博客ShiftSync社区。请回复blogathon话题。截图。

          

          2. 创建原始的博客文章(之间300 - 1000字)和覆盖下列主题之一:

          • 移动应用程序的自动化测试-这是一个广泛的话题,所以随意选择自己的观点:它如何有助于公司的成功或分享一些例子从你的经验(正面或挑战和经验)。
          • 足够的测试是什么?
          • 集成在c# Microservices OAuth 2.0:一个循序渐进的指南。

          3. 遵守规则:

          • 一个作家可以提交多个博客;然而,他们必须盖上面列出的主题
          • 入口应该在英语
          • 不应该有多个作者的条目
          • 别忘了提到博客的标题,你选择
          • 请包括图像(不超过5)使你的博客视觉吸引力。您可以使用图像pexels或unsplash

          谁可以投票?

          • 任何人
          • 你不能投票自己的博客但继续并激活您的网络和朋友,让他们把票投给你,让你的名字和文章列表的顶部!

          标题:测试自动化移动应用程序,他们的挑战和一些工具
          

          

          随着人口增长和技术,手机用户的数量也迅速增长给各种各样的移动应用程序开发人员需要引入新功能,使应用程序更加可伸缩的、安全的、功能齐全的和许多其他的东西。

          但随着市场的快速要求,保持良好的质量在一个期限有时成为一个繁忙的工作,为开发人员和时间可能会有一些遗漏的范围。

          填补空白的原型到最终产品的测试是必需的,但我告诉你由于增加的需求。最终产品的测试和分布以非常快的速度需要做。的帮助和理解,只有手工测试是有点困难,可能会花费一些时间比理想。

          移动应用程序的自动化测试,手工测试团队所做的工作可以自动化,使流程更有效率,还整个规模部署在一个更好的方法。

          现在,这看起来有趣的声音和相当简单。但自动化的问题是当你想做一个基本任务与小规则是不错,但它适合更多的规则和实施更多的检查。然后自动化过程变得比听起来更复杂一点。

          但是与自动化测试可以实现很多东西,例如:可以节省大量的时间,多线程或可以同时运行多个测试用例,对重复场景相同的测试用例可以多次使用和许多更多。

          让我们听听苦的一面,这是挑战移动应用程序的自动化测试:
          ——频繁和更快的新功能的要求。
          ——支持多种平台/操作系统。
          ——无缝集成和功能
          和更多。
          
          让我们看一看不同的工具,可以用来做移动应用程序的自动化测试:-
          

          1. Appium:开源移动Android和iOS应用程序的自动化测试工具。它支持本地、移动网络和混合应用程序使用WebDriver接口,允许平台之间的代码重用。

          2. Robotium:另一个开源的Android应用程序测试的工具。它写道:强大的基于java的快速混合动力和本地应用的测试用例。

          3. MonkeyRunner:为框架设计/功能测试的Android应用程序,提供无需多设备控制等功能,回归测试,基于python脚本。

          4. UI Automator:由谷歌Android UI用于功能测试用例,开发支持设备从Android 4.1起。

          5. Android Selendroid:领先的自动化测试软件的混合,本地和188金宝搏官网登录app移动web应用程序无需多设备交互。

          6. MonkeyTalk:自动化功能测试与用户友好的脚本,Android和iOS应用程序XML / HTML报告和截图截图所示。

          7. Testdroid:基于云计算的移动应用测试平台为iOS和Android设备使用不同的配置,降低开发成本,提高软件质量。

          8. 葫芦:支持. net, Ruby, Flex, Java,和更多的测试本机与黄瓜混合移动应用集成框架。

          9. 弗兰克:侧重于测试iOS应用程序,结合JSON和黄瓜,并提供详细的应用程序信息的应用程序督察“Symbioate。”

          10. 甜美:网站和移动应用程序跨平台的测试自动化工具,支持iOS、Android,塞班,黑莓和Windows Phone。

          11. Kobiton:协助与真实设备测试,建立一流的移动体验appium脚本生成、实验室和设备管理。

          12. SmartBear TestComplete:功能自动化测试平台的软件网络,Android, iOS和Windows应用程序。188金宝搏官网登录app

          13. 咖啡:谷歌的Android应用程序的开源自动化测试框架,以其简单性和可伸缩性。

          14. Ranorex工作室:一个强大的基于web的GUI自动化测试框架,移动和桌面应用程序,利用c#和VB.NET这样的语言。

          15. 茄子:AI-assisted测试工具确保快速应用程序版本,业务连续性和可伸缩性与云支持。

          最后但不是最少,什么事情要牢记,编写自动化脚本为移动应用程序是:
          
          移动应用自动化测试需要使用设备和操作系统优先级的分析数据,包括至少一个设备/屏幕尺寸范围,测试各种网络速度优化性能,效率分解方案,使用代码组织哦,进行一致的高质量应用程序测试。以下这些做法确保无缝的用户体验和成功应用。
          
          

          

          \t

          <\/figure>

          We're thrilled to announce our first\u00a0blogathon , and we warmly invite you to participate and showcase your exceptional technical and writing skills!<\/p>\t

          This is not your average competition, folks. It's a chance to connect with like-minded individuals, flaunt your expertise, give your article\u00a0the spotlight it deserves, and who knows, you might just snag some\u00a0prizes along the way!<\/p>\t

          To encourage more people towards blog writing, ShiftSync is launching a one-month Blogathon contest from July 19, 2023, to August 18, 2023<\/strong>.\u00a0<\/p>\t

          \t

          \t

          \t

          \t

          \t

          \t

          \t

          \t

          \t

          \t

          Top 3 winners will get monetary prizes, badges, and certificates of recognition.\u00a0\u00a0<\/p>\t

          • \t\t

            \ud83e\udd47First prize \u2013 300 USD + Swag\u00a0<\/p>\t\t<\/li>\t\t

          • \t\t

            \ud83e\udd48Second prize \u2013 150 USD\u00a0+ Swag\u00a0<\/p>\t\t<\/li>\t\t

          • \t\t

            \ud83e\udd49Third prize \u2013 50 USD\u00a0+ Book of the industry expert\u00a0<\/p>\t\t<\/li>\t<\/ul>

            In addition, we will have some outstanding entries who will receive certificates of participation and ShiftSync badges (based on your points).\u00a0<\/p>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>

            \u00a0If you have any concerns or need assistance, feel free to reach out to shiftsync@tricentis.com<\/a>\u00a0or message\u00a0@Kat<\/user-mention>\u00a0or\u00a0@Daria<\/user-mention>.<\/p>\t

            \t

            \t

            \t

            \t

            \t

            \t

            \t

            \t

            \t

            \t

            You must watch out for these dates<\/strong>:\u00a0<\/p>\t

            • \t\t

              Blog submission last date \u2013 July 30, 2023\u00a0<\/p>\t\t<\/li>\t\t

            • \t\t

              ShiftSync assessment \u2013 August 16, 2023\u00a0<\/p>\t\t<\/li>\t\t

            • \t\t

              Winner announcement \u2013 August 18, 2023\u00a0<\/p>\t\t<\/li>\t<\/ul><\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>

              After blog submission, you can vote for your fellow users\u2019 blogs. The most popular blogs in terms of likes and comments will be shortlisted. Public voting is open for 14 days (about 2 weeks) after submission. In other words, if you submit the blog on July 19, your votes will be counted for 14 days, starting from July 19\u00a0to August 1. If you submit your blog on July 30, you will still get 14 days of voting, which means your votes will be counted from July 30 till August 12.\u00a0\u00a0<\/p>\t

              Please make sure that you submit your blogs on or before July 30, 2023. Post July 30, your blogs won\u2019t be accepted.\u00a0\u00a0<\/span><\/strong><\/p>\t

              \t

              \t

              \t

              \t

              \t

              \t

              \t

              \t

              \t

              ShiftSync will finalize the top 3 winners based on public voting.\u00a0<\/strong>\u00a0<\/p>\t

              An opportunity for you all to create blogs on the new community and win prizes. We\u2019re encouraging you to create some meaningful and engaging content with utmost brevity. Get ready to awaken your creative muse. Grab the opportunity to educate your fellow users as well as encourage them to be a part of it.\u00a0\u00a0<\/p>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>

              How to be a part of this Blogathon?\u00a0<\/h3>\t

              1. \t\t

                 Submit your blog to the ShiftSync community.<\/u><\/a> Please reply to the blogathon topic. Screenshot attached.\u00a0<\/p>\t\t<\/li>\t<\/ol>

                 <\/figure>

                 \u00a0<\/p>\t

                 1. Create your original blog posts (between 300-1000 words<\/strong>) and cover ONE of the following topics:\u00a0<\/li>\t<\/ol>
                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    • \ud83d\udcc3Test Automation for Mobile Applications<\/strong> \u2013This is a broad topic, so feel free to pick your own point of view: from how it contributes to company success or share some examples from your experience (both positive or challenges and learnings).<\/li>\t\t
                    • \ud83d\udcc3What's enough testing?<\/strong><\/li>\t\t
                    • \ud83d\udcc3Integrating OAuth 2.0 in C# Microservices: A Step-by-Step Guide.<\/strong>\u00a0<\/li>\t<\/ul><\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>
                      1. Follow the rules:<\/li>\t<\/ol>
                         • An author can submit multiple blogs; however, they must cover the topics listed above\u00a0\u00a0\u00a0<\/li>\t\t
                         • The entry should be in English\u00a0<\/li>\t\t
                         • The entry should not have multiple authors\u00a0<\/li>\t\t
                         • Don't forget to mention the title of the blog that you chose\u00a0\u00a0<\/li>\t\t
                         • Please include images (not more than 5) to make your blog visually appealing. You can use images from pexels<\/u><\/a> or unsplash<\/u><\/a>\u00a0<\/li>\t<\/ul>

                           Who can vote?\u00a0<\/strong><\/p>\t

                           • Anyone\u00a0<\/li>\t\t
                           • You cannot vote your own blog but go ahead and activate your network and friends, have them vote for you and get your name and article to the top of the list!\u00a0<\/li>\t<\/ul><\/div><\/content-quote>

                             TITLE: Testing Automation for Mobile Apps, Their Challenges and Some Tools to Do It\u00a0<\/strong>
                             \u00a0<\/p>

                             <\/figure>

                             \u00a0<\/p>

                             With the ever growing population and technology,\u00a0the amount of mobile users is also rapidly increasing giving the need for various mobile application developers to introduce new features, make the application more scalable, secure, fully functional and many other things.\u00a0<\/p>

                             But with the rapid requirement of the market, maintaining a good quality under a deadline sometime becomes a hectic job for developers and that time there may be something that is left out of scope.\u00a0<\/p>

                             To fill in the gaps of the prototype to final product a lot of testing is required but as I\u00a0told you due to the increasing requirement. The testing and distribution of final product needs to be done at a very fast rate. And to comprehend that with the help of only manual testing is a little hard and may be little time consuming than ideal.\u00a0<\/p>

                             It is where the Automated Testing of Mobile Apps, The work done manual testing team can be automated to make the process more efficient and also scale the whole deployment in a better way.\u00a0<\/p>

                             Now, the sound of this does seems interesting and fairly simple. But the problem with automation is when you are trying to do a basic task with little rules it is good but to make it appropriate for a larger number of rules and implementing more check. Then the automation process becomes a little more complex than it sounds.\u00a0<\/p>

                             But nonetheless with automation testing a lot of things can be achieved such as:\u00a0a lot of time can be saved, multi threading or multiple test cases can run simultaneously, For repeated scenarios same test cases can be used multiple times and many more.\u00a0<\/p>

                             Let\u2019s hear the bitter side of it, which are challenges to the automated testing of mobile application:\u00a0
                             --Frequent and faster requirement of new features.
                             --Support Multiple Platforms\/OS.\u00a0
                             --Seamless Integration and Functionality\u00a0
                             and some more.\u00a0
                             
                             Let\u2019s Have a look at different tools that are available\u00a0to do the automated testing of mobile applications:-\u00a0
                             \u00a0<\/p>

                             1. \t

                                Appium: An open-source mobile test automation tool for Android and iOS apps. It supports native, mobile web, and hybrid apps using WebDriver interface, allowing code reuse between platforms.<\/p>\t<\/li>\t

                             2. \t

                                Robotium: Another open-source tool for Android app testing. It writes powerful Java-based test cases for hybrid and native apps quickly.<\/p>\t<\/li>\t

                             3. \t

                                MonkeyRunner: Designed for framework\/functional testing of Android apps, offering features like multi-device control, regression testing, and Python-based scripting.<\/p>\t<\/li>\t

                             4. \t

                                UI Automator: Developed by Google for functional Android UI test cases, supporting devices from Android 4.1 onwards.<\/p>\t<\/li>\t

                             5. \t

                                Selendroid: Leading test automation software for Android's hybrid, native, and mobile web apps with multi-device interaction.<\/p>\t<\/li>\t

                             6. \t

                                MonkeyTalk: Automates functional testing for Android and iOS apps with user-friendly scripts, XML\/HTML reporting, and screenshot capture.<\/p>\t<\/li>\t

                             7. \t

                                Testdroid: Cloud-based mobile app testing platform for iOS and Android devices with different configurations, reducing development costs and improving app quality.<\/p>\t<\/li>\t

                             8. \t

                                Calabash: Supports .NET, Ruby, Flex, Java, and more to test native and hybrid mobile apps with Cucumber framework integration.<\/p>\t<\/li>\t

                             9. \t

                                Frank: Focuses on testing iOS apps, combining JSON and Cucumber, and provides detailed app information with the app inspector \"Symbioate.\"<\/p>\t<\/li>\t

                             10. \t

                                 SeeTest: A cross-platform test automation tool for websites and mobile apps, supporting iOS, Android, Symbian, Blackberry, and Windows Phone.<\/p>\t<\/li>\t

                             11. \t

                                 Kobiton: Assists in building top-notch mobile experiences with real device testing, appium script generation, and device lab management.<\/p>\t<\/li>\t

                             12. \t

                                 TestComplete: A functional automated testing platform by SmartBear Software for Web, Android, iOS, and Windows apps.<\/p>\t<\/li>\t

                             13. \t

                                 Espresso: Google's open-source test automation framework for Android apps, known for its simplicity and scalability.<\/p>\t<\/li>\t

                             14. \t

                                 Ranorex Studio: A powerful GUI test automation framework for web-based, mobile, and desktop apps, utilizing languages like C# and VB.NET.<\/p>\t<\/li>\t

                             15. \t

                                 Eggplant: An AI-assisted testing tool ensuring fast app release, business continuity, and scalability with cloud support.<\/p>\t<\/li><\/ol>

                                 Last but not the least, what things to be kept in mind while writing automation scripts for mobile apps are:\u00a0
                                 
                                 Automating mobile app testing requires using analytics data for device and OS prioritization, including at least one device per screen size range, testing various network speeds for optimal performance, breaking down scenarios for efficiency, using OOPS for code organization, and conducting consistent testing for high app quality. Following these practices ensures a seamless user experience and a successful application.
                                 
                                 \u00a0<\/p>

                                 <\/figure>

                                 \u00a0<\/p>","quoteUsername":"Rishabh","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                                 • 就像
                                 • 报价和回复

                    ---

                    

                    • arunkumardutta
                    • 亚音速0.7
                    • 3回复
                    • 8天前

                      2023年7月29日

                    嗨 @Kat——我无法把我的博客文章,因为它显示30000个字符限制。试着回复和报价&回复。词女士说包括空格它有5 k字符。附上截图,供您参考。请做必要的。非常感谢您的支持。

                    

                    Hi @Kat<\/user-mention>\u00a0- I am unable to post my blog article as it is showing 30000 Character limits. Tried with both Reply and Quote & Reply.\u00a0 MS Word says including spaces it is having 5K Characters. Attached the screenshot for your reference. Please do the needful. Thank you so much\u00a0for your support.<\/p>

                    <\/figure>

                    \u00a0<\/p>","quoteUsername":"arunkumardutta","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                    • 就像
                    • 报价和回复

                    ---

                    

                    • arunkumardutta
                    • 亚音速0.7
                    • 3回复
                    • 7天前

                      2023年7月29日

                    

                    

                    

                    

                    ---

                    

                    Userlevel 5

                    + 2

                    • anuvip
                    • 0.8跨声速
                    • 20个回复
                    • 7天前

                      2023年7月29日

                    

                    我们非常高兴宣布第一blogathon,我们热忱邀请您参与,展示你的特殊技术和写作技巧!

                    这不是普通的竞争,人。这是一个机会与志趣相投的人,炫耀你的专长,给你的文章应有的关注,谁知道呢,你可能只是抓拍一些奖品!

                    鼓励更多的人向博客写作,ShiftSync推出一个月Blogathon比赛2023年7月19日,2023年8月18日。

                    前三赢家将获得货币奖励,徽章,和证书的认可。

                    • 一等奖- 300美元+赃物

                    • 二等奖- 150美元+赃物

                    • 三等奖- 50美元+书行业的专家

                    此外,我们将有一些杰出的条目将获得证书的参与和ShiftSync徽章(根据你的点)。

                    如果你有任何问题或需要帮助,随时联系shiftsync@188金宝搏app苹果下载软件tricentis.com或消息 @Kat或 @Daria。

                    你必须小心这些日期:

                    • 博客提交过去的日子——2023年7月30日

                    • ShiftSync评估——2023年8月16日

                    • 赢家- 8月18日宣布,2023年

                    博客提交之后,可以把票投给你的用户的博客。最受欢迎的博客而言,喜欢和评论将入围。公众投票开放14天提交后(约2周)。换句话说,如果你提交博客7月19日,你的投票数为14天,从7月19日至8月1日。如果你提交你的博客7月30日,你仍然会得到14天的投票,这意味着你的票将会从7月30日到8月12日计算。

                    请确保你在7月30日或之前提交您的博客,2023人。7月30日,你的博客不会被接受。

                    ShiftSync将完成基于公众投票前三的赢家。

                    你所有的机会在新创建的博客社区,赢得奖品。我们鼓励你创建一些有意义的和引人入胜的内容极其简洁。准备唤醒你的创作灵感。抓住机会让你的用户以及鼓励他们成为它的一部分。

                    如何成为一个Blogathon的一部分吗?

                    1. 提交你的博客ShiftSync社区。请回复blogathon话题。截图。

                    

                    2. 创建原始的博客文章(之间300 - 1000字)和覆盖下列主题之一:

                    • 移动应用程序的自动化测试-这是一个广泛的话题,所以随意选择自己的观点:它如何有助于公司的成功或分享一些例子从你的经验(正面或挑战和经验)。
                    • 足够的测试是什么?
                    • 集成在c# Microservices OAuth 2.0:一个循序渐进的指南。

                    3. 遵守规则:

                    • 一个作家可以提交多个博客;然而,他们必须盖上面列出的主题
                    • 入口应该在英语
                    • 不应该有多个作者的条目
                    • 别忘了提到博客的标题,你选择
                    • 请包括图像(不超过5)使你的博客视觉吸引力。您可以使用图像pexels或unsplash

                    谁可以投票?

                    • 任何人
                    • 你不能投票自己的博客但继续并激活您的网络和朋友,让他们把票投给你,让你的名字和文章列表的顶部!

                    

                    没有这个话题听起来简单吗?人会说,当你停止寻找bug,测试应该停止,或者当执行了所有的测试,通过测试就够了。许多其他理论也可以成为答案。当我们完成测试,或者觉得它完成,新的测试的想法。因此它是非常重要的,知道什么时候停止测试。以我的经验作为一个初级测试员、高级测试人员和测试经理了20多年,我发现一些方法,你可以发现如果执行足够的测试。

                    1. 所有会议中讨论的测试思想,或者由经理或扔在测试之间实现:-你经历的每个示例场景和故事来测试都来了。这意味着你只由其他人创建的测试用例执行。这可能感觉剩下的东西,通常是在团队中与许多老年人和初级测试人员。初级测试人员被要求保持在测试的范围,因此他们知道何时停止当测试完成的列表。
                    2. 测试时间已经过去:-SDLC,敏捷和其他实践到位,测试通常是一个时间约束的活动。随着市场竞争加剧,有人可以宣布时间和软件需要发货。188金宝搏官网登录app不管你喜欢与否,我们有一个有限的时间进行测试,所以这些可能是好指标,是停止的时候了。在这种情况下,测试是基于优先级的测试用例。
                    3. 测试是不会产生理想的结果:-它是几个月的一遍又一遍地重复同样的测试。可能已经实现了自动化。如果管理已经停止添加新功能,测试也不用做一样的。你知道即使有错误隐藏,这将是一个非常简单的错误因此没有必要浪费资源测试。我们可以停止。
                    4. 疲劳测试人员:年底的一天,还是对产品寿命结束时,测试人员可以感到筋疲力尽,我们应该停止的时间。如果我不能找到一个错误今天5 - 6小时后测试,很可能我失去焦点,因为我精神疲惫。我可能想要停止测试,今天,明天,继续。
                    5. 无关紧要的测试思想:有时前面的测试思想,我们把管理可以被我们听到这些测试不值得和产品可以忍受任何错误相关的测试。在这种情况下我们可以停止测试特定的功能区域。

                    除了一般的指导方针,还有其他几种情况,确定软件测试的程度和持续时间。188金宝搏官网登录app进行一系列测试后你可能会满意质量的代码或错误比例但事实上可能是一个完全不同的画面。质量、缺陷比例等可以在反对派指出方向。如果你释放软件在这种状态下,它可能是昂188金宝搏官网登录app贵,不利于你的业务。你可以控制它通过评估发现更多的缺陷的可能性。这是推断的分析结果。分析是很重要的,因为

                    ●新发现的缺陷是一个强烈的迹象继续测试他们常常导致其他缺陷。

                    ●如果你发现缺陷与整体功能的一小部分,你应该继续测试。

                    ●如果多个测试软件的功能不展示任何缺陷,那么它就是正确的时间停止测试软件。188金宝搏官网登录app

                    ●将停止软件测试之前,您需要确保它的重要特性主要或完全188金宝搏官网登录app令人满意的性能进行测试。

                    ●一个人应该总是依靠全面的测试和结果,而不是他们的决定基于一个错误的信心单板。它并不少见,很多开发人员完全跳过测试说明只要代码执行;它已经达到了验收测试基准。

                    成功来自于早期识别风险。这是一个很好的指标,软件测试何时停止。188金宝搏官网登录app风险因素将决定你的测试水平。如果在各种测试像单元测试、系统测试、回归测试等,你得到了积极的结果,你可以停止测试。

                    我们可以很容易地推测你能理解软件测试是时候停止当你有信心找到任何额外的缺陷和各种测试时给你一个高度的信心,准备发布的软件。188金宝搏官网登录app

                    结论:

                    它可以很容易地看到,没有预定义的规则,您可以使用每次找到多少测试是足够的。可视化项目情况,项目准备和时间自己决定。

                    质量的主张,一些

                    \t

                    <\/figure>

                    We're thrilled to announce our first\u00a0blogathon , and we warmly invite you to participate and showcase your exceptional technical and writing skills!<\/p>\t

                    This is not your average competition, folks. It's a chance to connect with like-minded individuals, flaunt your expertise, give your article\u00a0the spotlight it deserves, and who knows, you might just snag some\u00a0prizes along the way!<\/p>\t

                    To encourage more people towards blog writing, ShiftSync is launching a one-month Blogathon contest from July 19, 2023, to August 18, 2023<\/strong>.\u00a0<\/p>\t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    \t

                    Top 3 winners will get monetary prizes, badges, and certificates of recognition.\u00a0\u00a0<\/p>\t

                    • \t\t

                      \ud83e\udd47First prize \u2013 300 USD + Swag\u00a0<\/p>\t\t<\/li>\t\t

                    • \t\t

                      \ud83e\udd48Second prize \u2013 150 USD\u00a0+ Swag\u00a0<\/p>\t\t<\/li>\t\t

                    • \t\t

                      \ud83e\udd49Third prize \u2013 50 USD\u00a0+ Book of the industry expert\u00a0<\/p>\t\t<\/li>\t<\/ul>

                      In addition, we will have some outstanding entries who will receive certificates of participation and ShiftSync badges (based on your points).\u00a0<\/p>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>

                      \u00a0If you have any concerns or need assistance, feel free to reach out to shiftsync@tricentis.com<\/a>\u00a0or message\u00a0@Kat<\/user-mention>\u00a0or\u00a0@Daria<\/user-mention>.<\/p>\t

                      \t

                      \t

                      \t

                      \t

                      \t

                      \t

                      \t

                      \t

                      \t

                      \t

                      You must watch out for these dates<\/strong>:\u00a0<\/p>\t

                      • \t\t

                        Blog submission last date \u2013 July 30, 2023\u00a0<\/p>\t\t<\/li>\t\t

                      • \t\t

                        ShiftSync assessment \u2013 August 16, 2023\u00a0<\/p>\t\t<\/li>\t\t

                      • \t\t

                        Winner announcement \u2013 August 18, 2023\u00a0<\/p>\t\t<\/li>\t<\/ul><\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>

                        After blog submission, you can vote for your fellow users\u2019 blogs. The most popular blogs in terms of likes and comments will be shortlisted. Public voting is open for 14 days (about 2 weeks) after submission. In other words, if you submit the blog on July 19, your votes will be counted for 14 days, starting from July 19\u00a0to August 1. If you submit your blog on July 30, you will still get 14 days of voting, which means your votes will be counted from July 30 till August 12.\u00a0\u00a0<\/p>\t

                        Please make sure that you submit your blogs on or before July 30, 2023. Post July 30, your blogs won\u2019t be accepted.\u00a0\u00a0<\/span><\/strong><\/p>\t

                        \t

                        \t

                        \t

                        \t

                        \t

                        \t

                        \t

                        \t

                        \t

                        ShiftSync will finalize the top 3 winners based on public voting.\u00a0<\/strong>\u00a0<\/p>\t

                        An opportunity for you all to create blogs on the new community and win prizes. We\u2019re encouraging you to create some meaningful and engaging content with utmost brevity. Get ready to awaken your creative muse. Grab the opportunity to educate your fellow users as well as encourage them to be a part of it.\u00a0\u00a0<\/p>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>

                        How to be a part of this Blogathon?\u00a0<\/h3>\t

                        1. \t\t

                           Submit your blog to the ShiftSync community.<\/u><\/a> Please reply to the blogathon topic. Screenshot attached.\u00a0<\/p>\t\t<\/li>\t<\/ol>

                           <\/figure>

                           \u00a0<\/p>\t

                           1. Create your original blog posts (between 300-1000 words<\/strong>) and cover ONE of the following topics:\u00a0<\/li>\t<\/ol>
                              \t

                              \t

                              \t

                              \t

                              \t

                              \t

                              \t

                              \t

                              \t

                              \t

                              • \ud83d\udcc3Test Automation for Mobile Applications<\/strong> \u2013This is a broad topic, so feel free to pick your own point of view: from how it contributes to company success or share some examples from your experience (both positive or challenges and learnings).<\/li>\t\t
                              • \ud83d\udcc3What's enough testing?<\/strong><\/li>\t\t
                              • \ud83d\udcc3Integrating OAuth 2.0 in C# Microservices: A Step-by-Step Guide.<\/strong>\u00a0<\/li>\t<\/ul><\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/div>\t<\/section>
                                1. Follow the rules:<\/li>\t<\/ol>
                                   • An author can submit multiple blogs; however, they must cover the topics listed above\u00a0\u00a0\u00a0<\/li>\t\t
                                   • The entry should be in English\u00a0<\/li>\t\t
                                   • The entry should not have multiple authors\u00a0<\/li>\t\t
                                   • Don't forget to mention the title of the blog that you chose\u00a0\u00a0<\/li>\t\t
                                   • Please include images (not more than 5) to make your blog visually appealing. You can use images from pexels<\/u><\/a> or unsplash<\/u><\/a>\u00a0<\/li>\t<\/ul>

                                     Who can vote?\u00a0<\/strong><\/p>\t

                                     • Anyone\u00a0<\/li>\t\t
                                     • You cannot vote your own blog but go ahead and activate your network and friends, have them vote for you and get your name and article to the top of the list!\u00a0<\/li>\t<\/ul><\/div><\/content-quote>

                                       

                              ---

                              

                              Userlevel 1

                              • hungoboss
                              • 亚音速0.5
                              • 3回复
                              • 6天前

                                2023年7月30日

                              为什么桅杆是必须的?

                              移动应用程序是件很大的事。现在几乎所有的应用程序。想知道这首歌你听在最近一个收音机吗?或者你的位置最近的有轨电车车站是什么吗?或与你的伴侣见面有一天当他/她声称他们去健身房呢?嗯,有一个应用程序。但这不是今天的主题的文章。2022年超过2550亿移动应用下载,没有否认,移动应用普遍。这使得大量的移动应用程序的压力测试。这并不意味着只有功能测试,但非功能性测试。 In today’s article, I’d like to talk about security testing and show an example of how an attacker can leverage a poorly tested application.

                              介绍这个问题

                              想象你是一个小公司想出了主意来创建一个应用程序,允许用户对他们去过的酒吧和酿酒厂。由于巨大的流行的Android在你的目标用户群,你决定创建一个应用程序在Android上,发布它在谷歌播放,用户下载应用程序。

                              许多人认为移动应用安全的天性。开发人员通常编写Java代码(或芬兰湾的科特林),编译,包和其他东西一起和发布可执行文件。可执行文件是不可读的混乱的组合为一个正常的人类。如果出现严重错误的发展期间,没有人能够弄清楚对吧?错了。

                              让我们返回我们的故事。公司能够发布应用程序,但它也引起了一些阴暗的家伙的注意在互联网上。我们将这些人的角色。我们必须获得的第一件事是应用程序本身。幸运的是,有APKpure等网站让我们获得它们。

                              

                              但被下载的文件只是一个上年。为了获得代码,攻击者会使用一个反编译器是一个软件,它允许我们相反的过程代码编译。188金宝搏官网登录app有各种各样的反编译器可用,但在这种情况下一个简单的JADX Java(敏捷)解码器应该足够了。关于这个工具是伟大的,它也有一个GUI版本使逆向工程过程更加容易。

                              

                              有一个代码,攻击者可以在数据库中寻找有趣的部分。在这种情况下,它可能是秘密。秘密是例如密码数据库或一个API令牌您可能使用的第三方服务。这是你不会想要任何攻击者染指。有很多方法,一个攻击者寻找秘密。其中一个将编写一个简单的正则表达式查找字符串与给定的模式(例如AWS令牌的形式通常是„AKIA”紧随其后16字符,可以是数字或大写字母)。在这个例子中,我们有一个商业秘密扫描仪。

                              

                              一个简单的错误,可以避免在开发阶段被发现从最终的可执行文件。在最坏的情况,这个错误可以降低小公司和他们的服务。这让很多emphacise测试和更特别的一个自动化的安全测试。

                              桅杆作为解决方案

                              所以现在我们已经解释了一个真实的场景,并展示了这个问题,我们也应该谈论如何预防它。和预防应该开始在开发各种自动桅杆工具的使用。我们使用术语桅杆,但究竟代表什么?

                              桅杆是„移动应用程序安全性测试”,它应该是每个组织的移动应用程序开发过程的一部分。它包括各种工具的组合,可以使用自动整个SDLC的构建和测试阶段。大多数这些工具可以完美地集成到CI / CD和根据他们的输出,我们可以让构建失败不满足安全需求。

                              谈到工具,让我们做一个简单介绍一下每个工具类别:

                              • 静态应用程序安全性测试(科协)用于识别漏洞扫描应用程序源代码。这些工具可以真正在你运行CI / CD或甚至一个IDE插件在编码和视为„白盒测试。
                              • 动态应用程序安全性测试(DAST)用于在运行时检查安全测试常见的攻击类型对正在运行的应用程序。科协相比,他们只能用在之后的开发过程,是一个„黑盒”测试。
                              • 交互式应用程序安全性测试(IAST)通过应用程序在运行时用于检查安全扫描和分析内部应用程序流。这是一个混合的白盒和黑盒测试的创建链接DAST科协源代码扫描。
                              • 188金宝搏官网登录app软件成分分析(SCA)用于跟踪第三方代码依赖项,这是有用的,当您的解决方案依赖于许多开源库。开发人员可以使用这些工具来发现组件,支持库和间接依赖关系可能导致缺陷和可能的漏洞。

                              理想情况下,你想要把这些工具放在您的开发在继承这样的管道:

                              

                              结论

                              随着移动应用的兴起,我不仅是重要的执行功能测试,但安全性测试。考虑攻击向量的大小,唯一可行的办法是使用自动化测试工具,可以执行各种扫描活动贯穿你的整个开发阶段。

                              Why MAST is a must?<\/span><\/h1>

                              Mobile applications are a huge deal these days. Nowadays there is an app for almost everything. Want to know what was the song you\u2019ve listened to on a radio recently? Or what is the nearest tram station to your location right now? Or with whom did your partner meet the other day when he\/she claimed they went to the gym alone? Well, there is an app for that as well. But that is not the topic of today\u2019s article. With over 255 billion mobile applications downloaded in 2022, there is just no denial that mobile applications are prevalent. This puts a lot of pressure on the mobile application testing. That doesn\u2019t mean only the functional testing, but the non-functional testing as well. In today\u2019s article, I\u2019d like to talk about security testing and show an example of how an attacker can leverage a poorly tested application.<\/p>

                              Introducing the problem<\/span><\/h2>

                              Imagine you are a small company that came up with the idea to create an app that would allow the users to rate the pubs and breweries they have visited. Due to the immense popularity of Android within your target user group, you have decided to create an application on Android, publish it on Google Play and have the users download the app from there.<\/p>

                              Many people perceive the mobile applications as secure by nature. The developers usually write the Java (or Kotlin) code, compile it, bundle it together with other stuff and publish it as an executable file. An executable file is just the combination of unreadable mess for a normal human being. If something goes horribly wrong during the development, no one should be able to figure that out right? Wrong.<\/p>

                              Let\u2019s return back to our story. The company was able to publish the application, but it also attracted the attention of some shady guys on the internet. We will play the role of these individuals. The first thing we have to obtain is the application itself. Luckily, there are sites such as APKpure that allows us to obtain them.<\/p>

                              <\/figure>

                              But the file that gets downloaded is just an APK. In order to get to the code, the attacker would use a decompiler which is a software that allows us to the reverse process to code compilation. There are various decompilers available, but in this case a simple JADX (Dex to Java) decompiler should do the trick. What is great about this tool is that it also has a GUI version which makes the reverse engineering process much easier.<\/p>

                              <\/figure>

                              Having a code available, the attacker can start looking for interesting parts within the database. In this case, it might be the secrets. Secret is for example a password for a database or an API token the third party service you might be using. It is something you wouldn\u2019t want any attacker to get their hands on. There are many ways for an attacker to look for secrets. One of them would be write a simple regex looking for strings with a given pattern (for example AWS tokens are usually in the form of \u201eAKIA\u201d followed by 16 characters that can be either numbers or capital letters). In this example, we have a commercial secret scanner.<\/p>

                              <\/figure>

                              A simple mistake that could have been prevented right in the development phase was discovered from the final executable. In the worst case scenario, this mistake could bring down the small company and their service. This puts a lot of emphacise on testing and more specifically an automated security testing.<\/p>

                              MAST as solution<\/h3>

                              So now that we have explained a real-life scenario and showcased the probl\u00e9m, we should also speak about how to prevent it. And the prevention should start during the development by the usage of various automatic MAST tools. We have used the term MAST, but what exactly does it stand for?<\/p>

                              MAST is \u201eMobile application security testing\u201c and it should be part of every organization\u2019s mobile application development process. It consists of the combination of various tools that can be used automatically throughout the build and testing phase of the SDLC. Most of these tools can be seemlessly integrated into the CI\/CD and based on their output, we can let the build fail for not meeting the security requirements.<\/p>

                              Speaking about tools, let\u2019s do a quick rundown of each tool category:<\/p>

                              • Static application security testing (SAST)<\/strong> is used for scanning the application source code to identify the vulnerabilities. These tools can be run really early in your CI\/CD or even as an IDE plugin while coding and are considered as \u201ewhite box\u201c testing.<\/li>\t
                              • Dynamic application security testing (DAST) <\/strong>is used for checking the security at runtime by testing common attack types against the running apps. In comparison to SAST, they can only be used much later in the development process and are an example of a \u201eblack box\u201c testing.<\/li>\t
                              • Interactive application security testing (IAST) <\/strong>is used for checking security at runtime via application scanning and analysis of internal application flows. It is a blend of white box and blackbox testing as it links the foundings of DAST to the source code scanned by SAST.<\/li>\t
                              • Software composition analysis (SCA) <\/strong>is used for tracking third-party code dependencies, which is useful when your solution relies on many open source libraries. Developers can use these tools to discover components, their supporting libraries and indirect dependencies that might result in vulnerabilities and possible exploits.<\/li><\/ul>

                                Ideally, you would like to put these tools into your development pipeline in the succession like this one:<\/p>

                                <\/figure>

                                Conclusion<\/h3>

                                With the rise of mobile applications, i tis vital to perform not only the functional testing, but the security testing as well. Considering the magnitude of attack vectors, the only feasible way forward is to use automated testing tools that can perform various scanning activities throughout your whole development phase.<\/p>","quoteUsername":"hungoboss","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                                • 就像
                                • 报价和回复

                              ---

                              B

                              Userlevel 5

                              • bhomiajayesh
                              • 亚音速0.7
                              • 2回答
                              • 6天前

                                2023年7月30日

                              足够的测试是什么?

                              

                              测试:这个词可以用作同义词修复问题。在软件188金宝搏官网登录app开发中,测试方法评估产品和验证产品做它应该做什么。

                              但是现在一百万美元的问题!

                              什么时候我们需要停止测试或什么足够的测试吗?

                              答案在于2因素:质量保证功能以及如何小心翼翼地,功能是用于测试为“质量比数量更重要!”

                              ”足够的测试”是指数量的测试,以保证软件产品满足需求定义。188金宝搏官网登录app

                              测试是发现错误和使用正确的测试用例允许这个。这也增加了工作的有效性和增加了100%的准确率,但不能保证无错的结果。

                              在我看来,有两个主要原因任何软件/应用程序不能完全测试。188金宝搏官网登录app

                              1. 对于一个特定的输入,可能会有“n”数量的测试,
                              2. 有太多的方式通过该产品可以进行测试。

                              测试的神话:

                              1. 知道,在会见客户的东西都是开发免费软件/应用程序错误:通常我们认为会议中讨论的点是足以让100%的准确率,但这是错误的。188金宝搏官网登录app可能会有一些极端情况,错过了在测试时。
                              2. 如果一个测试人员认为,他的作用是验证产品应该完全工作,然后他对自己所做的不公,因为在现实世界中任何程序不是百分百无缺陷。

                              大多数开发人员抓住和解决最大错误的产品在部署之前测试,所以测试人员发现其余的角色。这个假设,1%由开发人员可能会被忽视,因为他们认为最终用户不会使用该产品时进行路线但作为一个测试人员不能。主要的目标是有一个顶级稳定的产品。

                              定义足够的测试方法:

                              1. 时间测试了:同时提供工作的时间估计到客户机,这显然已经提到,这是分配给特定的测试程序和工作应该完成。
                              2. 在会议讨论的一些观点:有机会的新想法或由经理讨论,TLs或团队的其他成员足够的测试。
                              3. 脱落的结果:假如很久以前你停止寻找bug,和测试的想法你足够努力来运行,你认为他们会产生较低的结果。更好的是,即使他们确实有错误,错误会小,或者只发生在一个复杂的和罕见的设置。不值得继续测试。
                              4. 的想法放在桌上的范围或与给定的工作无关。

                              结论:虽然测试是一个永无止境的过程,但记住项目情况下,大量的工作,准备交付和项目期限可以被认为是决定何时停止测试。

                              What\u2019s enough testing?<\/strong><\/span><\/p>

                              \u00a0<\/p>

                              <\/strong><\/span><\/p>

                              \u00a0<\/p>

                              Testing<\/strong><\/span>: The term can be used as a synonym for fixing the problems. In Software Development, testing means evaluating the product and verifying that the product does what it's supposed to do.\u00a0<\/span><\/p>

                              But now a million dollar question arises!<\/span><\/p>

                              \u00a0<\/p>

                              At\u00a0 what time do we have to stop testing or what\u2019s <\/span>enough testing?<\/strong><\/span><\/p>

                              \u00a0<\/p>

                              The answer lies in 2 factors: the <\/span>QA functionality <\/strong><\/span>and how scrupulously that <\/span>Functionality is applied in testing<\/strong><\/span> as \u201c<\/span><\/span>Quality matters more than quantity!\u201d<\/em><\/span><\/span><\/p>

                              \u00a0<\/p>

                              \u201c<\/span>Enough Testing<\/strong><\/span>\u201d refers to the amount of testing which ensures that a software product meets the requirements as defined.\u00a0<\/span><\/p>

                              Testing is all about finding the errors and using the right test cases enables this. This increases the effectiveness of the work and also increases the accuracy rate but couldn\u2019t guarantee the 100% error free result.<\/span><\/p>

                              In my opinion, there are two main reasons why any software\/application can not be tested completely.<\/span><\/p>

                              1. For a particular input, there may be \u201cn\u201d number of tests and,<\/span><\/li>\t
                              2. There are too many ways through which the product can be tested.<\/span><\/li><\/ol>

                                 Testing Myths:<\/span><\/p>

                                 1. Know that, the things which are covered in the client meeting are all to develop the error free software\/application: Often we think that the points which are discussed in the meetings are enough to get the 100% accuracy but this is wrong. There might be few edge cases that were missed while testing.<\/span><\/li>\t
                                 2. If a tester feels that his role is to verify that the product should work perfectly, then he is doing injustice to himself because in the real world any program is not hundred percent bug free.<\/span><\/li><\/ol>

                                    Most of the developers catch and fix maximum of their mistakes in a product before deploying it for testing, so it is the role of the tester to find the remaining. This suppose, 1% may be neglected by the developers because they assume the end-user wouldn\u2019t take that route while using the product but as a tester you can\u2019t. The main goal is to have a top-level stable product.<\/span><\/p>

                                    Approaches to define Enough Testing:<\/strong><\/span><\/p>

                                    1. Time for the testing ran out: While providing the time estimation of the work to the client, it has been clearly mentioned that this is the time allotted for the testing of the particular program and work should be completed within it.<\/span><\/li>\t
                                    2. Ideas that were discussed in the meetings: There are chances that the new ideas which were given or discussed by the manager, TLs, or other members of the team were enough for testing.<\/span><\/li>\t
                                    3. Getting the fall off results: Suppose a long time ago you stopped finding bugs, and the test ideas which you have are sufficiently hard to run and you think they will yield lower results. Better yet, even if they did have errors, the errors would be small, or only happen with a complex and rare setup. It\u2019s not worth continuing testing.<\/span><\/li>\t
                                    4. Ideas put on the table were out of scope or unrelated to the given work.<\/span><\/li><\/ol>

                                       Conclusion<\/strong>: <\/span>\u00a0Although the testing is one of the never ending process but keeping in mind the\u00a0<\/span><\/span>project situations, the amount of work that is ready for delivery and project deadlines can be considered\u00a0to decide when to stop the testing.<\/span><\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>

                                       \u00a0<\/p>","quoteUsername":"bhomiajayesh","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                                       • 就像
                                       • 报价和回复

                              ---

                              

                              Userlevel 5

                              + 2

                              • 凯特
                              • 作者
                              • 社区经理
                              • 72回复
                              • 6天前

                                2023年7月31日

                              嗨 @Kat——我无法把我的博客文章,因为它显示30000个字符限制。试着回复和报价&回复。词女士说包括空格它有5 k字符。附上截图,供您参考。请做必要的。非常感谢您的支持。

                              

                              你好,这个问题可能在图像是否太大。请发布文章少(或更好)的照片。

                              质量问题,凯特

                              \t

                              Hi\u00a0@Kat<\/user-mention>\u00a0- I am unable to post my blog article as it is showing 30000 Character limits. Tried with both Reply and Quote & Reply.\u00a0 MS Word says including spaces it is having 5K Characters. Attached the screenshot for your reference. Please do the needful. Thank you so much\u00a0for your support.<\/p>\t

                              <\/figure>

                              \u00a0<\/p>\t<\/div><\/content-quote>

                              Hi, the problem may be in images if they are too large. Please just\u00a0publish the article with less (or better without) pictures.\u00a0<\/p>","quoteUsername":"Kat","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                              • 就像
                              • 报价和回复

                              ---

                              

                              • arunkumardutta
                              • 亚音速0.7
                              • 3回复
                              • 5天前

                                2023年7月31日

                              嗨 @Kat——我无法把我的博客文章,因为它显示30000个字符限制。试着回复和报价&回复。词女士说包括空格它有5 k字符。附上截图,供您参考。请做必要的。非常感谢您的支持。

                              

                              你好,这个问题可能在图像是否太大。请发布文章少(或更好)的照片。

                              嗨 @Kat——谢谢你的回应。我试着发布文档没有图像按你的建议。它被提交,但是无法在此页面查看提交的文档。请让我知道需要做什么。谢谢!

                              \t

                              \t\t

                              \t\t

                              Hi\u00a0@Kat<\/user-mention>\u00a0- I am unable to post my blog article as it is showing 30000 Character limits. Tried with both Reply and Quote & Reply.\u00a0 MS Word says including spaces it is having 5K Characters. Attached the screenshot for your reference. Please do the needful. Thank you so much\u00a0for your support.<\/p>\t\t

                              <\/figure>

                              \u00a0<\/p>\t\t<\/div>\t\t<\/div>\t<\/content-quote>

                              Hi, the problem may be in images if they are too large. Please just\u00a0publish the article with less (or better without) pictures.\u00a0<\/p>\t<\/div><\/content-quote>

                              Hi @Kat<\/user-mention>\u00a0- Thank you for your response.\u00a0I tried to publish the document without image\u00a0as per your suggestion. It got submitted, however unable to view the submitted document\u00a0in this page. Please let me know what needs to be done. Thanks!<\/p>","quoteUsername":"arunkumardutta","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                              • 就像
                              • 报价和回复

                              ---

                              

                              Userlevel 5

                              + 2

                              • 凯特
                              • 作者
                              • 社区经理
                              • 72回复
                              • 5天前

                                2023年8月1

                              嗨 @Kat——我无法把我的博客文章,因为它显示30000个字符限制。试着回复和报价&回复。词女士说包括空格它有5 k字符。附上截图,供您参考。请做必要的。非常感谢您的支持。

                              

                              你好,这个问题可能在图像是否太大。请发布文章少(或更好)的照片。

                              嗨 @Kat——谢谢你的回应。我试着发布文档没有图像按你的建议。它被提交,但是无法在此页面查看提交的文档。请让我知道需要做什么。谢谢!

                              我给你

                              质量问题,凯特

                              \t

                              \t\t

                              \t\t

                              \t\t\t

                              \t\t\t

                              \t\t\t

                              Hi\u00a0@Kat<\/user-mention>\u00a0- I am unable to post my blog article as it is showing 30000 Character limits. Tried with both Reply and Quote & Reply.\u00a0 MS Word says including spaces it is having 5K Characters. Attached the screenshot for your reference. Please do the needful. Thank you so much\u00a0for your support.<\/p>\t\t\t

                              <\/figure>

                              \u00a0<\/p>\t\t\t<\/div>\t\t\t<\/div>\t\t\t<\/div>\t\t<\/content-quote>

                              Hi, the problem may be in images if they are too large. Please just\u00a0publish the article with less (or better without) pictures.\u00a0<\/p>\t\t<\/div>\t\t<\/div>\t<\/content-quote>

                              Hi\u00a0@Kat<\/user-mention>\u00a0- Thank you for your response.\u00a0I tried to publish the document without image\u00a0as per your suggestion. It got submitted, however unable to view the submitted document\u00a0in this page. Please let me know what needs to be done. Thanks!<\/p>\t<\/div><\/content-quote>

                              I messaged you\u00a0\ud83d\ude0a<\/p>","quoteUsername":"Kat","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                              • 就像
                              • 报价和回复

                              ---

                              

                              Userlevel 5

                              + 2

                              • 凯特
                              • 作者
                              • 社区经理
                              • 72回复
                              • 4天前

                                2023年8月2

                              

                              这篇文章是写的 @arunkumardutta

                              作品简介:

                              在IT行业工作超过17.5年后全球许多地区的作为一个测试人员和出版超过64的博客文章,2社区图书,20 +国际会议和11个全球网络研讨会,我还是觉得“足够的测试”是一个非常引人深思的话题。

                              早在2020年8月,我在欧洲之星蜷缩发表了一篇文章——“测试一切是不可能的”(https://huddle.eurostar188金宝搏官网登录appsoftwaretesting.com/testing-everything-is-impossible/)。在这篇文章中,我谈到了“在当今快节奏的行业,加速交付是生存的唯一途径,测试一切或每一个组合是不可能的。即使在最有利的情况下,我们假设我们测试了所有的东西,总是会有丢失的东西的机会。在这两种情况下,持续的监控将协助发现失踪的情况下在实际最终用户之前提前和积极影响”。

                              我很高兴Tricentis S188金宝搏app苹果下载软件hiftSync正在进行首次Blogathon竞赛,要求测试社区钢笔他们想到这个有趣的话题——“足够的测试”。

                              

                              足够的测试——是不可能:

                              而毫无疑问,即便在SDLC——软件开发生命周期的最后阶段,我们可以证实,我们进行了足够的测试和不需要更多的测试。188金宝搏官网登录app我们甚至不能说没有任何更多的错误或问题,我们已经进行了足够的测试。即使是在一个软件测试188金宝搏官网登录app人员的梦想这是不可能的。

                              如果我们仔细观察,有很多可能的组合的测试(许多技术平台,许多操作系统,浏览器,很多设备,许多版本,许多网络)和测试所有这些仅仅是高不可攀。是的,利用自动化增加价值,可以节省大量的时间,但即便如此,测试所有的这些是不可能进行短距离的冲刺时间在加速交付。添加额外的资源也不可能由于项目预算。早测试,常测试,测试速度快,测试尽可能测试即使在生产和测试正确的事情将总体目标。

                              我个人认为总质量比数量更重要。所以,我们不应该思考什么是足够的测试,当我们可以说足够的测试完成,我们应该考虑产品的最终用户。作为测试人员,我们的目标是确保最终用户是快乐的不同质量属性功能,性能、安全性、可用性、可用性、可靠性、可访问性。

                              足够的测试,没有数据点,而同意作为一个团队:

                              简单,既不存在(或有)任何数据点什么是足够的测试。足够的测试只是一个同意后由一组不同类型的测试人员进行不同类型的测试在指定的时间内上线。最后,我想说的是,没有这样的公式或数据点进行足够的测试。

                              我认为测试人员应该在一个破坏性的软件产品的态度,让它更强大和更好的终端用户。188金宝搏官网登录app

                              最后,验证软件产品成为生188金宝搏官网登188金宝搏官网app注册录app活只有当产品风险进行不同类型的综合测试和作为一个团体都同意搬到生产。

                              足够的测试,综合测试策略文档可以帮助:

                              虽然我们的测试人员,不能说足够测试完成。然而,测试人员可以确认是否应用程序将生活毕竟他们的测试思想全面测试,其次是作为一个团队的讨论。

                              请注意,测试应该是每个人的工作——当我说每个人,我是说从架构师,开发人员,数据库的人不同类型的测试人员操作产品负责人团队商人——字面上的每一个人。

                              测试思想包括所有积极的,消极的,适用的开箱即用的思维场景和所有这些必须在指定的时间进行如上所述的测试策略文档。综合测试策略文档是有用的去生活在一个生产环境,但不够展开的测试(无论多么全面的测试思想,总是会有一个机会错过一些测试的想法)。

                              足够的测试——持续的监控可以帮助:

                              而足够的确认测试是不可能的,在所有方面——持续的监控

                              答:连续测试的项目监控过程(进步,比较,优先顺序,确认)。

                              b连续应用程序性能监控——仪表板、趋势图、自动警报积极解决这些问题在所有应用程序组件,api,接口之前影响终端用户。

                              c .连续安全监视,再次确定安全漏洞,源代码,攻击之前提前影响终端用户。

                              d .满栈可观测性,得到完整的能见度在整个生活系统。

                              对我来说,什么是足够的测试在当今世界被视为完整的堆栈可观测性主动支持终端用户。

                              结论:

                              虽然我不知道足够的测试是即使作为一个充满激情的试验机工作了这么长时间但对我来说足够的测试是全面测试策略、合作作为一个整体团队,朝着全栈可观测性,确保3 e-enhanced的终端用户体验,忍受长期在市场上建立一个品牌。

                              关于Arun Kumar Dutta

                              阿伦有超过17年半管理端到端性能测试交付经验。他一直选择在多个国际测试会议和全球网络研讨会。他的全球测试多个博客已发表在不同的论坛。此外,他贡献了2社区书在全球范围内与其他神奇的测试人员。他还赢得了各种内部和外部的奖项。

                              目前作为一名副主任在LTIMindtree企业性能和弹性测试实践。

                              质量问题,凯特

                              <\/figure>

                              The article is written by @arunkumardutta<\/user-mention>\u00a0<\/strong><\/em><\/p>

                              Introduction:<\/span><\/strong><\/span><\/p>

                              After working in the IT industry over 17.5 years as a tester across many parts of the globe and publishing over 64 blog articles, 2 community books, 20+ international conferences and 11 global webinars, I still feel that \u201cwhat\u2019s enough testing\u201d is a very thought-provoking topic.<\/span><\/p>

                              Back in Aug 2020, I published an article in EuroSTAR Huddle \u2013 \u201cTesting everything is impossible\u201d (https:\/\/huddle.eurostarsoftwaretesting.com\/testing-everything-is-impossible\/<\/span><\/a>). In that article, I talked about \u201cIn today\u2019s fast paced industry, where accelerating delivery is the only way to survive, testing everything or every combination is simply impossible. Even in most favourable cases, where we assume that we tested everything, there will always be a chance of missing something. In both cases, continuous monitoring will assist to uncover missing cases well in advance and proactively before the actual end-users are affected.\u201d<\/span><\/p>

                              I am glad that Tricentis ShiftSync is conducting its first Blogathon contest and asked the testing community to pen down their thought about this interesting topic- \u201cwhat\u2019s enough testing\u201d.<\/span><\/p>

                              <\/figure>

                              Enough testing- is simply Impossible:<\/span><\/strong><\/span><\/p>

                              While there is no doubt that even at the last stages of SDLC- Software Development Life Cycle, we can confirm that we conducted enough testing and there is no more testing required. We even can\u2019t say that there will not be any more bugs or issues as we already conducted enough testing. Even in a software tester\u2019s dream this is impossible.<\/span><\/p>

                              If we look closely, there are so many possible combinations of testing (many technology platforms, many operating systems, many browsers, many devices, many versions, many networks) and testing all these is simply unattainable. Yes, leveraging automation adds value and can save an incredible amount of time but even still, testing all of these is not possible to conduct in a shorter sprint duration in accelerated delivery. Adding additional resources is also not possible due to the project budget. Test early, test often, test fast, test as much as possible, test even in production and test the right things will be the overall objective.<\/span><\/p>

                              I personally think quality always matters more than quantity. So, we should not think about what enough testing is and when we can say enough testing done rather, we should think about the product end-users. As a tester, our objective is to ensure that end-users are happy in terms of different quality attributes like functionality, performance, security, usability, availability, reliability, accessibility for example.<\/span><\/p>

                              Enough testing- No Data points rather Consent as a Team:<\/span><\/strong><\/span><\/p>

                              Simply, neither there is (or there will be) any data points for what enough testing is. Enough testing is just a consent by a group of different types of testers after conducting different types of testing in a specified time frame to go live. Ultimately, what I am trying to say is that there is no such formula or data points for enough testing. <\/span><\/p>

                              I think testers should be in a destructive attitude towards the software product to make it stronger and better for its end-user.<\/span><\/p>

                              At the end, software products become live only when product risks are verified by conducting different types of comprehensive testing and as a group all agree to move to production.<\/span><\/p>

                              Enough testing- Comprehensive Test Strategy Document can assist:<\/span><\/strong><\/span><\/p>

                              While we, the testers, can\u2019t say ever that enough testing is done. However, testers can confirm whether applications will be live or not after all their test ideas are thoroughly tested, followed by discussion as a team. <\/span><\/p>

                              Please note that testing should be everyone\u2019s job- when I say everyone, I mean starting from architect to developers, database folks to different types of testers to product owners to operation team to businesspeople - literally everyone. <\/span><\/p>

                              Test ideas include all positive, negative, and applicable out of box thinking scenarios and all these must be conducted in a specified time as mentioned on the test strategy document. So, a comprehensive test strategy document is helpful to go live in a production environment but not unfolding what\u2019s enough testing is (as no matter how comprehensive test ideas are, there will always be a chance to miss some test ideas). <\/span><\/p>

                              Enough testing- Continuous Monitoring can assist:<\/span><\/strong><\/span><\/p>

                              While enough testing is impossible to confirm, continuous monitoring in all aspects- <\/span><\/p>

                              a. continuous project monitoring of the test process (progress, compare, re-prioritize, confirm).<\/span><\/p>

                              b. continuous application performance monitoring- dashboards, trending charts, automated alerts for proactively resolving the issues across all application components, APIs, Interfaces even before impacting end-users.<\/span><\/p>

                              c. continuous security monitoring \u2013 again to identify security vulnerabilities, source code, attacks in advance before it affects end-users.<\/span><\/p>

                              d. full stack observability- to get full visibility across the whole live system.<\/span><\/p>

                              For me, what\u2019s enough testing in today\u2019s world is seen as full stack observability to proactively support end-users.<\/span><\/p>

                              Conclusion:<\/span><\/strong><\/span><\/p>

                              While I don\u2019t know what\u2019s enough testing is even after working as a passionate tester for so long but for me what\u2019s enough testing is a combination of comprehensive test strategy, collaborative as a whole team and moving towards full stack observability to ensure 3E-enhanced end-user experience, endure in the market for long to establish as a brand. <\/span><\/p>

                              About Arun Kumar Dutta<\/span><\/strong><\/span><\/p>

                              Arun has over 17 and half years of managing end to end performance testing delivery experiences. He has been selected in multiple international testing conferences and global webinars. His multiple blogs have been published in different global testing forums.\u00a0 Additionally, he contributed to 2 community books with other amazing testers across the globe.\u00a0 He also won various internal and external awards. <\/span><\/p>

                              Currently working as an Associate Director at Enterprise Performance & Resiliency Testing Practice in LTIMindtree.<\/span><\/p>","quoteUsername":"Kat","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                              • 就像
                              • 报价和回复

                              ---

                              D

                              • 书中
                              • 1回复
                              • 2天前

                                2023年8月4日

                              足够的测试是什么?

                              

                              测试:这个词可以用作同义词修复问题。在软件188金宝搏官网登录app开发中,测试方法评估产品和验证产品做它应该做什么。

                              但是现在一百万美元的问题!

                              什么时候我们需要停止测试或什么足够的测试吗?

                              答案在于2因素:质量保证功能以及如何小心翼翼地,功能是用于测试为“质量比数量更重要!”

                              ”足够的测试”是指数量的测试,以保证软件产品满足需求定义。188金宝搏官网登录app

                              测试是发现错误和使用正确的测试用例允许这个。这也增加了工作的有效性和增加了100%的准确率,但不能保证无错的结果。

                              在我看来,有两个主要原因任何软件/应用程序不能完全测试。188金宝搏官网登录app

                              1. 对于一个特定的输入,可能会有“n”数量的测试,
                              2. 有太多的方式通过该产品可以进行测试。

                              测试的神话:

                              1. 知道,在会见客户的东西都是开发免费软件/应用程序错误:通常我们认为会议中讨论的点是足以让100%的准确率,但这是错误的。188金宝搏官网登录app可能会有一些极端情况,错过了在测试时。
                              2. 如果一个测试人员认为,他的作用是验证产品应该完全工作,然后他对自己所做的不公,因为在现实世界中任何程序不是百分百无缺陷。

                              大多数开发人员抓住和解决最大错误的产品在部署之前测试,所以测试人员发现其余的角色。这个假设,1%由开发人员可能会被忽视,因为他们认为最终用户不会使用该产品时进行路线但作为一个测试人员不能。主要的目标是有一个顶级稳定的产品。

                              定义足够的测试方法:

                              1. 时间测试了:同时提供工作的时间估计到客户机,这显然已经提到,这是分配给特定的测试程序和工作应该完成。
                              2. 在会议讨论的一些观点:有机会的新想法或由经理讨论,TLs或团队的其他成员足够的测试。
                              3. 脱落的结果:假如很久以前你停止寻找bug,和测试的想法你足够努力来运行,你认为他们会产生较低的结果。更好的是,即使他们确实有错误,错误会小,或者只发生在一个复杂的和罕见的设置。不值得继续测试。
                              4. 的想法放在桌上的范围或与给定的工作无关。

                              结论:虽然测试是一个永无止境的过程,但记住项目情况下,大量的工作,准备交付和项目期限可以被认为是决定何时停止测试。

                              \t

                              What\u2019s enough testing?<\/strong><\/span><\/p>\t

                              \u00a0<\/p>\t

                              <\/strong><\/span><\/p>\t

                              \u00a0<\/p>\t

                              Testing<\/strong><\/span>: The term can be used as a synonym for fixing the problems. In Software Development, testing means evaluating the product and verifying that the product does what it's supposed to do.\u00a0<\/span><\/p>\t

                              But now a million dollar question arises!<\/span><\/p>\t

                              \u00a0<\/p>\t

                              At\u00a0 what time do we have to stop testing or what\u2019s <\/span>enough testing?<\/strong><\/span><\/p>\t

                              \u00a0<\/p>\t

                              The answer lies in 2 factors: the <\/span>QA functionality <\/strong><\/span>and how scrupulously that <\/span>Functionality is applied in testing<\/strong><\/span> as \u201c<\/span><\/span>Quality matters more than quantity!\u201d<\/em><\/span><\/span><\/p>\t

                              \u00a0<\/p>\t

                              \u201c<\/span>Enough Testing<\/strong><\/span>\u201d refers to the amount of testing which ensures that a software product meets the requirements as defined.\u00a0<\/span><\/p>\t

                              Testing is all about finding the errors and using the right test cases enables this. This increases the effectiveness of the work and also increases the accuracy rate but couldn\u2019t guarantee the 100% error free result.<\/span><\/p>\t

                              In my opinion, there are two main reasons why any software\/application can not be tested completely.<\/span><\/p>\t

                              1. For a particular input, there may be \u201cn\u201d number of tests and,<\/span><\/li>\t\t
                              2. There are too many ways through which the product can be tested.<\/span><\/li>\t<\/ol>

                                 Testing Myths:<\/span><\/p>\t

                                 1. Know that, the things which are covered in the client meeting are all to develop the error free software\/application: Often we think that the points which are discussed in the meetings are enough to get the 100% accuracy but this is wrong. There might be few edge cases that were missed while testing.<\/span><\/li>\t\t
                                 2. If a tester feels that his role is to verify that the product should work perfectly, then he is doing injustice to himself because in the real world any program is not hundred percent bug free.<\/span><\/li>\t<\/ol>

                                    Most of the developers catch and fix maximum of their mistakes in a product before deploying it for testing, so it is the role of the tester to find the remaining. This suppose, 1% may be neglected by the developers because they assume the end-user wouldn\u2019t take that route while using the product but as a tester you can\u2019t. The main goal is to have a top-level stable product.<\/span><\/p>\t

                                    Approaches to define Enough Testing:<\/strong><\/span><\/p>\t

                                    1. Time for the testing ran out: While providing the time estimation of the work to the client, it has been clearly mentioned that this is the time allotted for the testing of the particular program and work should be completed within it.<\/span><\/li>\t\t
                                    2. Ideas that were discussed in the meetings: There are chances that the new ideas which were given or discussed by the manager, TLs, or other members of the team were enough for testing.<\/span><\/li>\t\t
                                    3. Getting the fall off results: Suppose a long time ago you stopped finding bugs, and the test ideas which you have are sufficiently hard to run and you think they will yield lower results. Better yet, even if they did have errors, the errors would be small, or only happen with a complex and rare setup. It\u2019s not worth continuing testing.<\/span><\/li>\t\t
                                    4. Ideas put on the table were out of scope or unrelated to the given work.<\/span><\/li>\t<\/ol>

                                       Conclusion<\/strong>: <\/span>\u00a0Although the testing is one of the never ending process but keeping in mind the\u00a0<\/span><\/span>project situations, the amount of work that is ready for delivery and project deadlines can be considered\u00a0to decide when to stop the testing.<\/span><\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\t

                                       \u00a0<\/p>\t<\/div><\/content-quote>

                                       \u00a0<\/p>","quoteUsername":"Dinesh","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

                                       • 就像
                                       • 报价和回复

                              ---

                              回复

                              
                              

                              由Gainsight

                              ShiftSync条款和条件

                              报名

                              已经有一个帐户吗?登录

                              用户名(之后不能修改)*

                              电子邮件地址*

                              名字*

                              姓

                              (私人)

                              只有你和版主可以看到这些信息

                              *

                              密码*

                              我同意接收营销传播根据隐私政策并同意Tricentis188金宝搏app苹果下载软件一般使用条款。

                              loginBox.register.email_repeat

                              注册

                              登录到社区

                              还没有账户?创建一个帐户

                              用户名或电子邮件

                              密码

                              记得我

                              登录

                              忘记了密码?

                              输入您的用户名或电子邮件地址。我们将送你一个电子邮件与指令重置你的密码。

                              用户名或电子邮件

                              发送 回到概述

                              病毒扫描文件。

                              对不起,我们仍然检查这个文件的内容,以确保它是安全的下载。请几分钟后再试一次。

                              好吧

                              这个文件不能下载

                              对不起,我们的病毒扫描器发现下载这个文件不是安全的。

                              好吧

                              Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
                              Functional","cookiepolicy.modal.level2":"Normal
                              Functional + analytics","cookiepolicy.modal.level3":"Complete
                              Functional + analytics + social media + embedded videos"}}}">

                              金宝搏app官网下载

                              不卖我的个人信息吗 隐私政策 法律信息 条款和条件