737 Matching Annotations
  1. Last 7 days
    1. Aleta, A., Martín-Corral, D., Pastore y Piontti, A., Ajelli, M., Litvinova, M., Chinazzi, M., Dean, N. E., Halloran, M. E., Longini Jr, I. M., Merler, S., Pentland, A., Vespignani, A., Moro, E., & Moreno, Y. (2020). Modelling the impact of testing, contact tracing and household quarantine on second waves of COVID-19. Nature Human Behaviour, 1–8. https://doi.org/10.1038/s41562-020-0931-9

    1. ReconfigBehSci. (2021, February 18). @ErikAngner I thought I joined the ‘conversation’ at the top- did I miss part of a prior thread? Post I responded to seemed to be the beginning of a thread...ie. ‘regular reminder that...’ [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1362385973603168257

    1. Jonathan Rothberg 🦋. (2021, March 2). Testing works. I test daily. Insist on HOME testing. @michaelmina_lab @JoeBiden Research suggests B.1.526 needs to be closely watched “for its ability to evade both monoclonal antibody and, to a certain extent, the vaccine-induced antibody,” said Fauci [Tweet]. @JMRothberg. https://twitter.com/JMRothberg/status/1366755339912306688

    1. Testing your designs is also crucial step during this process.
    2. Remember, even the email clients with better HTML and CSS support have their own individual quirks and still require testing to see what’s possible.
    1. Hall, V. J., Foulkes, S., Saei, A., Andrews, N., Oguti, B., Charlett, A., Wellington, E., Stowe, J., Gillson, N., Atti, A., Islam, J., Karagiannis, I., Munro, K., Khawam, J., Chand, M. A., Brown, C. S., Ramsay, M., Lopez-Bernal, J., Hopkins, S., … Heeney, J. L. (2021). COVID-19 vaccine coverage in health-care workers in England and effectiveness of BNT162b2 mRNA vaccine against infection (SIREN): A prospective, multicentre, cohort study. The Lancet, 0(0). https://doi.org/10.1016/S0140-6736(21)00790-X

    1. Ashish K. Jha, MD, MPH. (2020, October 27). President keeps saying we have more cases because we are testing more This is not true But wait, how do we know? Doesn’t more testing lead to identifying more cases? Actually, it does So we look at other data to know if its just about testing or underlying infections Thread [Tweet]. @ashishkjha. https://twitter.com/ashishkjha/status/1321118890513080322

    1. Dr Nisreen Alwan 🌻. (2021, March 14). Exactly a year ago we wrote this letter in the Times. We were gobsmacked! We just didn’t understand what the government was basing all its decisions on including stopping testing and the herd immunity by natural infection stuff. We wanted to see the evidence backing them. [Tweet]. @Dr2NisreenAlwan. https://twitter.com/Dr2NisreenAlwan/status/1371168531669258242

  2. May 2021
  3. Apr 2021
    1. let(:warden) do instance_double('Warden::Proxy').tap do |warden| allow(warden).to receive(:authenticate!).with(scope: :user) .and_return(authenticated?) allow(warden).to receive(:user).with(:user).and_return(user) end end let(:user) { instance_double(User) } let(:authenticated?) { true } def simulate_running_with_devise stub_const( 'Rack::MockRequest::DEFAULT_ENV', Rack::MockRequest::DEFAULT_ENV.merge('warden' => warden), ) end
    2. There is no request.env in functional tests because the functional tests are supposed to remain at the controller level.
  4. Mar 2021
    1. There is obvious connections between the flow paths of a use case and its test cases. Deriving functional test cases from a use case through its scenarios (running instances of a use case) is straightforward.
    1. Larremore, D. B., Wilder, B., Lester, E., Shehata, S., Burke, J. M., Hay, J. A., Tambe, M., Mina, M. J., & Parker, R. (2020). Test sensitivity is secondary to frequency and turnaround time for COVID-19 surveillance. MedRxiv, 2020.06.22.20136309. https://doi.org/10.1101/2020.06.22.20136309

    1. Prof. Devi Sridhar. (2020, March 25). We will be stuck in an endless cycle of lockdown/release for next 18 months, if we do not start mass testing, tracing, & isolating those who are carriers of the virus while pursuing rapid research for antiviral treatment or vaccine. This is the message the public needs to hear. [Tweet]. @devisridhar. https://twitter.com/devisridhar/status/1242743618986745861

    1. Why separate out red tests from green tests? Because my green tests serve a fundamentally different purpose. They are there to act as a living specification, validating that the behaviors work as expected. Regardless of whether they are implemented in a unit testing framework or an acceptance testing framework, they are in essence acceptance tests because they’re based upon validating behaviors or acceptance criteria rather than implementation details.
    2. Conversely, red tests are tests I write after the code is written to lock down some implementation.
    3. Have you ever played the game 20 questions? Most of us have played that game at one point in our lives. One person thinks of something that could be an animal, vegetable, or mineral and then they answer yes/no questions that are asked of them. The point of the game is to ask as few questions as possible in order to accurately guess what the person is thinking.  This is how I think of the unit tests that I write the specified behavior as I’m doing test-first development. I ask what are the fewest tests that I need to write in order to assert the behavior I want to create.
    4. So the question becomes how many tests are enough?
    5. I am a big advocate of having a complete test base and even erring on the side of caution when it comes to quality engineering and software validation but that is not what we’re talking about here. What we’re talking about here are the tests that we write when we’re doing test-first development and I’m proposing that writing those tests from the perspective of specifying the behaviors that we want to create is a highly valuable way of writing tests because it drives us to think at the right level of abstraction for creating behavioral tests and that allow us the freedom to refactor our code without breaking it.
    6. The number one problem that I see developers have when practicing test-first development that impedes them from refactoring their code is that they over-specify behavior in their tests. This leads developers to write more tests than are needed, which can become a burden when refactoring code.
    1. Sometimes a change impact analysis is performed to determine an appropriate subset of tests

      Hey, I do that sometimes so I can run a smaller/faster subset of tests. Didn't know it had a fancy name though.

    2. non-regression testing

      That would probably be a better name because you're actually testing/verifying that there hasn't been any regression.

      You're testing for the absence of regression. But I guess testing for one also tests for the other, so it probably doesn't matter. (If something is not true you know it is false, etc.)

    3. Regression testing (rarely non-regression testing[1]) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change.[2] If not, that would be called a regression.
    1. In production, you will never trigger one specific callback or a particular validation, only. Your application will run all code required to create a Song object, for instance. In Trailblazer, this means running the Song::Create operation, and testing that very operation with all its side-effects.
    2. There’s no need to test controllers, models, service objects, etc. in isolation
    3. Run the complete unit with a certain input set, and test the side-effects. This differs to the Rails Way™ testing style, where smaller units of code, such as a specific validation or a callback, are tested in complete isolation. While that might look tempting and clean, it will create a test environment that is not identical to what happens in production.
    4. Integration tests for controllers: These Smoke tests only test the wiring between controller, operation and presentation layer.
    5. Unit tests for operations: They test all edge cases in a nice, fast unit test environment without any HTTP involved.
    6. This helper allows you to mock any step within a given or deeply nested activities.
    7. To skip processing inside :load_user and use a mock instead, use mock_step.
    1. Erich Neuwirth. (2020, November 11). #COVID19 #COVID19at https://t.co/9uudp013px Zu meinem heutigen Bericht sind Vorbemerkungen notwendig. Das EMS - aus dem kommen die Daten über positive Tests—Hat anscheinend ziemliche Probleme. Heute wurden viele Fälle nachgemeldet. In Wien gab es laut diesem [Tweet]. @neuwirthe. https://twitter.com/neuwirthe/status/1326556742113746950

  5. Feb 2021
    1. Miro Weinberger. (2020, December 3). Our 1st Covid-19 wastewater tests since Thanksgiving just came in—Virus levels are up significantly citywide. I hope that all of #BTV will look at this graph and see what I see: A call to action, to stop gathering with other households, and to get tested ASAP if you have https://t.co/8nxTwOOcFA [Tweet]. @MiroBTV. https://twitter.com/MiroBTV/status/1334613511692017664

    1. TRAILBLAZER-TEST The official stable release is only weeks away bringing you a bunch of new assertions that drastically reduce coding effort for tests! Of course, Minitest and RSpec will both be supported. TRAILBLAZER-STORY will follow as it turned out to be inevitable for setting up application state for tests. Instead of fumbling around with factories and traits in your tests, you “tell a story” about what to create in which order, easily customizable, and all written using activities. Currently, I’m working on designing the interfaces and it’s real fun!
  6. Jan 2021
    1. I think I'm seeing some weird behavior when I select "bill_length_mm" on this chart: check it out. Is that expected?

    1. // Arrange const [refDiv, contentDiv] = getElements(); const [refAction, contentAction, getInstance] = createPopperActions({ placement: 'right-start', }); mountWithAction(refDiv, refAction); // Act mountWithAction(contentDiv, contentAction); // Assert expect(getInstance()).not.toBeNull();
    1. Personally, I think you are perhaps blowing up a fairly medium-sized (and fixable) bug discovered during routine testing into extreme-case hyperbole. Again, engagement and participation will get the bug fixed faster. The entire point of testing is to discover and fix precisely these kinds of pain points before release.
  7. Dec 2020
    1. In a webinar hosted by MIT Sloan School of Management professor Andrew Lo on April 1, Bancel said that Moderna is already manufacturing mRNA for vaccines in its potential Phase II study, which could begin enrolling hundreds of people this spring, as well as its potential Phase III study, which could enroll thousands of people as early as late summer or early fall. In a US Securities and Exchange Commission filing the week before, Bancel also indicated that Moderna may request special permission to give people like doctors and nurses access to its vaccine this fall, before a formal approval. It’s an audacious plan for a company—and technology—that has yet to put a drug on the market.
  8. Nov 2020
    1. Comparison between pytest and unittes test frameworks

      Detailed comparison table of pytest vs unittest modules (check below)

    1. Today, more and more businesses are inclined towards react native due to the innumerable benefits it offers. React native apps have completely changed the mobile app development process but the performance of the app remains extraordinary as before.

      In this article, we will be talking about a few popular react native testing tools that will enhance your development process.

  9. Oct 2020